Project Management: Foundations to Practice · Scope Management and Work Breakdown Structures
Defining Scope
Ambiguous scope is one of the most reliable predictors of project conflict. This chapter covers what a genuine scope statement contains and why exclusions matter as much as inclusions.
Scope defines the boundaries of a project: what work is included, and just as importantly, what is explicitly excluded. A scope statement typically describes the project's deliverables, the major exclusions, and the acceptance criteria that will be used to determine whether the work is complete [1].
Key Takeaways
- A scope statement covers deliverables, explicit exclusions, and measurable acceptance criteria for determining completion.
- Stating exclusions explicitly, not just inclusions, closes off disputes where stakeholders assumed something was always included.
- Rigorous scope definition built on poor requirements gathering just formalizes a wrong understanding with more apparent confidence.
- Vague acceptance criteria like 'user-friendly' provide little protection; specific, testable criteria are needed to prevent late disputes.