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
Общее время
4
Уровни компетенций
12
Уроки
Чему вы научитесь
- 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
Программа
Проходите уровни компетенций по порядку.
1
Awareness
- 2mFrom needs to requirementsЗнания
- 2mThe scope statement: inclusions and exclusionsЗнания
- 7mAwareness check: requirements and scope statementsОценка
2
Knowledge
- 3mBreaking scope down: the WBS and the 100% ruleЗнания
- 3mWork packages and ownershipЗнания
- 8mKnowledge check: WBS and work packagesОценка
3
Skill
- 3mControlling scope creepЗнания
- 3mBuild a scope statement and WBS for a real projectЗадание
- 7mSkill check: defending the baselineОценка
4
Mastery
- 3mChange requests and the change control processЗнания
- 3mRun a change control cycle end to endЗадание
- 8mMastery assessment: scope under pressureОценка
Ready to build Scope Definition & Work Breakdown?
Создайте бесплатный аккаунт на iCompetent и начните проходить уровни уже сегодня.