Scope
Project scope defines the complete set of product increments to be delivered and all the work needed to create the finished product.
Key Points
- Combines what will be delivered (product increments) with the work required to deliver it.
- Clarified and refined iteratively through backlog refinement, planning, and acceptance criteria.
- Explicit boundaries and exclusions help prevent scope creep.
- Managed through artifacts like the scope statement and product backlog, with changes handled through formal change control or backlog updates.
Example
On a mobile banking app project, scope includes increments like login, balance view, and funds transfer, plus the work for UX design, API integration, testing, and deployment. Features such as bill pay are out of scope unless added and approved later.
PMP Example Question
Which statement best describes project scope on an agile project?
- The sprint schedule and team capacity.
- The complete set of product increments to be delivered and the work required to create them.
- Only the highest-priority user stories in the current sprint.
- The list of risks and issues tracked by the team.
Correct Answer: B - Complete deliverables and required work
Explanation: Scope covers both what is delivered (increments) and the work to produce it, not schedule, a single sprint's stories, or the risk register.
