Scope Definition & Work Breakdown
How to turn stakeholder needs into a clear scope statement and a deliverable-oriented work breakdown structure, and how to defend that scope through change control — for planners, engineers and project managers.
52m
Total time
4
Competency levels
12
Lessons
What you'll learn
- Gather requirements from stakeholders and prioritise them against the project's objectives
- Write a scope statement that states explicit inclusions and exclusions
- Decompose scope into a deliverable-oriented work breakdown structure that satisfies the 100% rule
- Define work packages with a single named owner and clear completion criteria
- Recognise and stop scope creep before it erodes the baseline
- Assess and route change requests through a formal change control process
Curriculum
Progress through each competency level in order.
1
Awareness
- 2mFrom needs to requirementsKnowledge
- 2mThe scope statement: inclusions and exclusionsKnowledge
- 7mAwareness check: requirements and scope statementsAssessment
2
Knowledge
- 3mBreaking scope down: the WBS and the 100% ruleKnowledge
- 3mWork packages and ownershipKnowledge
- 8mKnowledge check: WBS and work packagesAssessment
3
Skill
- 3mControlling scope creepKnowledge
- 3mBuild a scope statement and WBS for a real projectAssignment
- 7mSkill check: defending the baselineAssessment
4
Mastery
- 3mChange requests and the change control processKnowledge
- 3mRun a change control cycle end to endAssignment
- 8mMastery assessment: scope under pressureAssessment
Reviews
No one has reviewed this skill yet. If you have worked through it, yours would be the first.
There are no published reviews for this course yet.
Write a review
Checking your account…
Ready to build Scope Definition & Work Breakdown?
Create a free account on iCompetent and start progressing through the levels today.