Project scope defines the objectives, deliverables, tasks, boundaries, and limitations of work. It clarifies what belongs in a project and what does not. section 7.2.3
Use scope to make estimation and delivery more reliable:
- Clarify requirements and divide the work into manageable tasks. section 7.2.1
- Ask developers and project managers about dependencies, prerequisites, resources, and likely obstacles. section 7.2.3 section 7.2.1
- Communicate your understanding of the scope to the project manager before work begins. section 7.2.3
- Review estimates as new challenges appear, while allowing for uncertainty. section 7.2.1
Uncommunicated feature work
Adding features to improve quality without telling the project manager can create out-of-scope tasks, waste time, and increase the budget. section 7.2.3
Agile teams can also frame scope around the best solution deliverable within a sprint, especially when requirements are organized around a user goal rather than a fixed feature list. section 7.2.3
