Scope questions test whether you can turn a need into something deliverable and keep it under control. That means requirements management, the breakdown structures that decompose the work, and configuration management — the discipline that stops scope drifting without anyone noticing.
What scope covers in the PMQ
- Requirements capture, analysis, prioritisation (e.g. MoSCoW) and management
- Product, work and cost breakdown structures and how they relate
- Baselining scope and controlling changes to it
- Configuration management: identification, control, status accounting and audit
- Scope creep, and the change control that prevents it
Where candidates lose marks
Confusing a product breakdown structure (what) with a work breakdown structure (the work to make it).
Treating configuration management as version control of documents only. It controls the deliverables themselves.
Letting 'small' changes bypass change control — the definition of scope creep.
Free, timed, exam-style questions across the twelve PMQ topics — with an explanation for every answer and a per-topic breakdown at the end.
Start a free practice testScope questions, answered
What is the difference between a product breakdown structure and a work breakdown structure?
A product breakdown structure decomposes WHAT the project will produce — its deliverables. A work breakdown structure decomposes the WORK needed to produce them. Confusing the two is a frequent exam trap.
What is scope creep and how is it controlled?
Scope creep is the uncontrolled expansion of scope as changes slip in without being assessed. It is prevented by change control: every change is logged, its impact assessed, and it is formally approved before it is implemented.
The other eleven topics
Independent study material, not affiliated with or endorsed by APM. Always check the official APM website for the current syllabus. APM does not publish a fixed pass mark for the PMQ.