Turning a need into something deliverable and keeping it under control. That means requirements, the breakdown structures that decompose the work, and configuration management — the discipline that stops scope drifting.
What scope covers in the PFQ
- Capturing and prioritising requirements
- Product and work breakdown structures and how they relate
- Baselining scope and controlling changes to it
- Configuration management
- 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).
Letting 'small' changes bypass change control — the definition of scope creep.
Treating configuration management as document version control only.
Free, timed, exam-style questions across all ten PFQ topics — with an explanation for every answer and a per-topic breakdown.
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.
What is scope creep?
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 nine topics
Independent study material, not affiliated with or endorsed by APM. Always check the official APM website for the current syllabus.