Why test project management knowledge?
Project management titles vary widely. One company's "project manager" runs multi-million budgets while another's coordinates diaries. A short knowledge test shows quickly whether a candidate understands core concepts such as roles, scheduling, scope and accountability, so interviews can focus on judgement and real experience.
What this template covers
- Scrum: the Product Owner and Scrum Master roles, and sprint length.
- Scheduling: what the critical path is and why it sets the end date.
- Scope and constraints: scope creep and the iron triangle of scope, time and cost.
- Accountability: RACI matrices and who does what.
How to run it well
Decide what kind of PM you need. For an Agile team, weight Scrum and Kanban questions more heavily. For construction or engineering projects, add questions on Gantt charts, earned value and change control. Points per question let you make the important topics count for more without making the test longer.
Keep it to 10–15 questions and about 15 minutes. Senior candidates are busy, and a long test puts the best ones off. Use the results to shape the interview. If someone misses the critical path question, ask them how they would handle a slipping deadline and listen to how they reason about dependencies.
Who this test is for
Use it for project managers, Scrum Masters, Product Owners, delivery leads and PMO analysts. Consultancies use it to check contractors before putting them in front of clients, and internal teams use it to see who is ready to move from a team member role into running projects.
Make it yours
Edit questions to match your methodology and tools, or ask the AI generator for questions on PRINCE2, risk registers or stakeholder management. The same bank can feed an internal certification quiz for staff moving into delivery roles. Responses are timed, scored on the server and shown with per-question analytics.