Ask any experienced project manager what kills more projects than bad estimates, and most will say the same thing: scope creep. PM4020 is built around the idea that scope is not a document you write once and file away — it is a boundary you defend, formally, every time someone asks for "just one more small thing."
The scope management plan and the WBS
PM4020 teaches the full scope-definition sequence: collecting requirements from stakeholders, writing a scope statement that explicitly states what is included and excluded, and decomposing that scope into a work breakdown structure (WBS) — a hierarchical breakdown of deliverables into work packages small enough to estimate, assign, and track. Students practice the 100% rule: the WBS must capture 100% of the project's scope, no more and no less, and any work not represented on the WBS is, by definition, outside the project.
Change control as the scope-creep defense
Because stakeholders will always find new requirements they'd like included, PM4020 frames integration management's change-control process as the formal gate between "a new idea" and "an approved change." Every proposed change is logged, assessed for impact on schedule/cost/quality, routed through a change control board (CCB) or designated authority, and either approved (with the baseline updated) or rejected — but never simply absorbed into the work informally. This is the mechanism that turns scope management from a document into an enforceable discipline.
Key topics in PM4020
- Collecting requirements: interviews, focus groups, surveys, and requirements traceability matrices
- Writing a scope statement: deliverables, acceptance criteria, exclusions, and constraints
- Building a WBS: decomposition rules, the 100% rule, and work packages vs. control accounts
- WBS dictionary: defining each work package's scope, owner, and acceptance criteria in detail
- Scope creep vs. scope change: why undocumented "small additions" are the most dangerous kind
- Change control process: change request logging, impact assessment, CCB approval, and baseline updates
- Scope verification and validation: formal customer sign-off on completed deliverables
Working on a WBS, scope statement, or change-control case study?
Our project management experts build PM4020-level coursework with real WBS decomposition and scope-control rigor.
Worked example: a scope-creep scenario and the correct response
- Situation: Midway through a website redesign, the client asks the developer to "just add a quick blog section" during a routine status call
- Wrong response: Developer agrees informally and adds it to the sprint without updating the scope baseline or budget
- Correct response: Developer logs a formal change request, estimates the added hours and cost, routes it through the change control process for sponsor approval
- Outcome: Client either approves the added cost/timeline or defers the blog to a phase 2 — but the decision is documented and the baseline stays accurate
Get Help With PM4020
WBS decomposition, scope statements, change-control case studies — done with PMBOK rigor.
Place Your OrderView All ServicesRelated courses
Frequently asked questions
The 100% rule states that a work breakdown structure must include 100% of the work defined by the project scope — capturing all deliverables (internal, external, and interim) — and no more. Every level of decomposition must sum to 100% of the parent level's scope: if a project has three major deliverables, decomposing the first into sub-tasks that only account for 80% of that deliverable's scope violates the rule, because 20% of the work is now invisible to planning, estimating, and tracking. The same rule cuts the other way — including work that is not actually part of the approved scope ("gold-plating") also violates the 100% rule, since it means the WBS represents more than what was authorized. PM4020 treats this rule as the single most important quality check on any WBS, because a WBS that fails it will silently under- or over-estimate the whole project.
Both involve the project's scope growing beyond its original baseline, but the difference is entirely about process, not size. An approved scope change goes through the formal change-control process: it is documented as a change request, its impact on schedule, cost, and quality is assessed, it is reviewed by the change control board or designated authority, and — if approved — the scope baseline, schedule, and budget are formally updated to reflect it. Scope creep is exactly the same kind of addition made informally: a team member agrees to "just add this" during a conversation, with no documentation, no impact assessment, and no baseline update. The danger of scope creep isn't that the added work is bad — it's that the project's schedule and budget are now measuring performance against a baseline that no longer reflects the actual scope being delivered, making every subsequent status report inaccurate.