Project Scope Management Flashcards
1
Q
How to establish scope through requirements management
A
- Gather requirements from stakeholders
- Analyse requirements for gaps or conflicts
- Prioritise & justify requirements, separating Needs from Wants.
○ MoSCoW: Must, Should, Could or Won’t Have - Baseline: ensure stakeholders agree with what has or hasn’t been included
1
Q
How to define project scope
A
- Product Breakdown Structure identifies the scope of what will be delivered
○ Purely focussed on the outputs, not the work required to achieve them - Work Breakdown Structure captures the activities to be completed in order to deliver the project outputs. It’s often derived from the PBS.
○ e.g. you need to research suppliers, buy ingredients, mix & bake in order to deliver a cake
2
Q
How to manage scope through configuration management
A
- Configuration Management = Change Control
- Plan
○ Outline scope, identify items that need configuring/change control, and agree processes - Identify
○ Identify items to be controlled/managed e.g. project documents, software code, systems, project plans - Control
○ Manage the change - authorise and implement it in a controlled way
3
Q
Explain how a change control process works
A
- RIDRUD:
○ Request
○ Initial evaluation
○ Detailed evaluation
○ Recommendation
○ Update plans
○ Do/Implement