Country
You are in the Nigeria edition. Type your country to switch.
Nigeria
Loading every country…
No country matches. Check the spelling, or choose "Any country" for the Global edition.
Your learning profile
Project management · Lesson 3 of 9
Scope and the work breakdown structure
Scope is the boundary of the work: what the project will deliver and, just as importantly, what it will not. This lesson takes requirements into a scope statement, breaks the work into a work breakdown structure of work packages, applies the 100% rule, and shows how change control keeps scope creep in check.
This lesson is complete in writing. A video for it is on its way.
What you will learn
- By the end you can turn a list of requirements into a scope statement with clear exclusions.
- You can build a work breakdown structure and explain the 100% rule.
- You can define a work package and say what makes one usable.
- You can recognise scope creep and explain why it is dangerous.
- You can describe a change control process from request to updated plan.
Key terms in this lesson
- Scope statement
- A written description of what a project will deliver, the boundaries of the work, the main deliverables, the acceptance criteria and the things explicitly excluded.
- Work breakdown structure
- A hierarchical decomposition of all the work of a project into smaller pieces, ending in work packages that can be estimated, assigned and tracked.
- Work package
- The lowest level of a work breakdown structure: a defined piece of work that one person or team can own, estimate, schedule and report on.
- Scope creep
- The gradual, uncontrolled growth of a project's scope through small additions that are never formally approved, costed or given extra time.
- Change control
- The formal process by which a proposed change to a project's scope, schedule or budget is recorded, assessed for impact, approved or rejected, and then built into the plan.
- Step 1: From requirements to a scope statement, not started
- Step 2: The work breakdown structure and the 100% rule, not started
- Step 3: A worked WBS: the Delta Engineering office move, not started
- Step 4: Scope creep: how projects grow in the dark, not started
- Step 5: Change control: how a change becomes part of the plan, not started
About 10 min of reading
Step 1 of 5
From requirements to a scope statement
Opening this step…
Step 2 of 5
The work breakdown structure and the 100% rule
This step opens when you finish the one above.
Step 3 of 5
A worked WBS: the Delta Engineering office move
This step opens when you finish the one above.
Step 4 of 5
Scope creep: how projects grow in the dark
This step opens when you finish the one above.
Step 5 of 5
Change control: how a change becomes part of the plan
This step opens when you finish the one above.
Key takeaways
The key takeaways open when you finish every step.
Lesson quiz
5 questions. You need 85% to pass.
The quiz opens when you finish every step.
Read first
Stockertim Learn is education. It explains how investing works and never recommends buying or selling anything.
Popular this week: Basics: BeginnerNGX & Africa: Beginner