PMP Managing the WBS or Backlog to Prevent Scope Creep

Scope discipline matters because scope creep usually begins as a series of small informal additions that feel harmless in the moment. PMP questions in this area usually reward the project manager who protects the scope boundary without becoming unnecessarily rigid.

Use the WBS or Backlog as a Control Tool

Whether the project uses a WBS, backlog, or hybrid structure, the stronger answer usually:

• keeps the scope structure current
• makes priorities visible
• distinguishes committed work from ideas or requests
• prevents quiet expansion through informal additions

The weaker answer allows teams or stakeholders to slide new work into the plan simply because it seems small or useful.

    flowchart TD
	    A["New request or idea appears"] --> B{"Already within agreed scope?"}
	    B -->|Yes| C["Manage inside the current WBS or backlog"]
	    B -->|No| D["Route through prioritization or change control"]
	    C --> E["Maintain scope discipline"]
	    D --> E

Discipline Looks Different by Delivery Model

In predictive work, scope discipline may focus on baseline control and formal changes. In adaptive work, it may focus on backlog governance, release boundaries, and preventing the team from treating every new idea as current commitment. The principle is the same: keep clear control over what is in and what is not.

Example

An end user asks for “one small extra field” while a feature is nearly complete. The stronger move is to check whether the request belongs in the current committed scope and, if not, route it properly instead of slipping it in quietly.

Common Pitfalls

• Treating small changes as free.
• Confusing backlog existence with scope discipline.
• Losing track of what is committed now versus later.
• Allowing stakeholder pressure to bypass the agreed scope path.

Check Your Understanding

Sample Exam Question

Scenario: During delivery of a committed release, several stakeholders keep asking for “small additions” that seem individually manageable. The team has started adding some of them directly into the backlog item details without formally revisiting current commitments.

Question: What is the strongest project-manager action?

• A. Allow the additions to continue because each one is minor
• B. Restore scope discipline by distinguishing current commitments from new requests and routing additions through the proper prioritization or change path
• C. Remove stakeholder access to the backlog entirely
• D. Approve all additions if the team believes it can work harder

Best answer: B

Explanation: The strongest answer is B because PMP questions in this area reward control over incremental scope change. Small additions still consume capacity and can distort delivery commitments if they bypass governance.

Why the other options are weaker:

• A: Minor uncontrolled additions accumulate into scope creep.
• C: Stakeholder involvement is still needed; the problem is control, not visibility alone.
• D: Hopeful effort assumptions are weaker than disciplined commitment management.

Key Terms

• Scope discipline: Maintaining clear control over what work is currently committed.
• Scope creep: Uncontrolled expansion of scope without proper decision handling.
• Committed scope: The work currently approved for delivery or completion.