Scope
Chapter Seven
Learning Objectives:
- Scope must be clearly defined and approved before work begins; in adaptive projects, this may be done at a higher level.
- Requirements should be elicited from all stakeholders and prioritized based on the business case.
- A Work Breakdown Structure (WBS) or a backlog is used to structure and clarify scope depending on the project approach.
- The project manager ensures all required work—and only that work—is completed, avoiding gold plating.
- Changes to scope must be evaluated for impacts on schedule, cost, and other project constraints, with formal approval on plan-driven projects.
- Agile projects allow for scope flexibility, but added scope affects priorities and may push items to future releases.