Domain 2 of 3 · Chapter 2 of 10

Developing and Managing Scope

Unlock the complete study guide + 1,040 practice questions across 16 full exams.

Bundled into the existing Project Management Professional premium course — no separate purchase.

14-day money-back guarantee — no questions asked.

Included in this chapter:

  • Define, agree, then break down scope
  • Defining scope: elicit it, then bound it
  • From agreed scope to work packages
  • Managing scope: guard the agreed baseline
  • Exam-pattern recognition

The scope loop in predictive vs adaptive delivery

Scope movePredictive (plan-driven)Adaptive (agile)
Define scopeScope statement (deliverables, acceptance criteria, exclusions), traced by an RTMPrioritized product backlog, elicited and continuously refined
Agree on scopeStakeholders approve the scope baseline before build-outDefinition of done is the standing acceptance standard
Break down scopeWBS decomposes deliverables into work packages under the 100% ruleBacklog refinement splits epics and stories into iteration-sized items
Manage scopeRoute a new request through change control; update the baseline and WBS only if approvedAdd the request to the backlog; the product owner re-prioritizes by value

Decision tree

New request:inside the agreed scope?Proceed: alreadyplanned workPredictive or adaptive delivery?Change control approves it?Add to productbacklog; ownerre-prioritizesUpdate scope baseline+ WBS, then buildDo not build it;log the decisioninsideoutsidepredictiveadaptiveapprovedrejected
Cheat sheet

Cheat sheet

  • The scope statement defines deliverables, boundaries, and exclusions
  • Acceptance criteria are agreed as part of scope, not after delivery
  • In adaptive delivery the ordered backlog represents evolving scope
  • A definition of done sets the completeness standard for increments
  • Backlog refinement decomposes large items into ready, sized work
  • A requirements traceability matrix links each requirement to its deliverable
  • Scope is defined by eliciting requirements, not by assuming them
  • Secure stakeholder agreement on scope before building it out
  • New requests are weighed against the agreed scope, not silently absorbed
  • The WBS decomposes scope into manageable work packages
  • The WBS captures all of the scope and only the scope

Unlock with Premium — includes all practice exams and the complete study guide.

References

  1. PMP Examination Content Outline (June 2026)
  2. Scope Management Blog
  3. Requirements improved project performance Blog
  4. Scoping Out a Scope Statement Blog
  5. The Scrum Guide (2020) Whitepaper
  6. Requirement traceability, a tool for quality results Blog
  7. Work Breakdown Structure (WBS): Basic Principles Blog
  8. Influence of the scope statement on the WBS Blog
  9. Scope change control Blog
  10. Top Five Causes of Scope Creep Blog