Product Backlog
The Product Backlog is the single source of truth for what needs to be built in the product. It's a dynamic, ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made.
- Maintained and prioritized by the Product Owner
- Contains features, requirements, enhancements, and fixes
- Items are ordered by value, risk, priority, and necessity
- Never complete - evolves as the product and environment evolve
- Details, estimates, and order are refined continuously
Sprint Planning
Sprint Planning initiates the Sprint by laying out the work to be performed. This is created by the collaborative work of the entire Scrum Team.
- Time-boxed to a maximum of eight hours for a one-month Sprint
- Addresses two critical questions: What can be delivered? How will the work be achieved?
- Results in clear Sprint Goal and Sprint Backlog
- Team determines capacity and velocity for the upcoming Sprint
- Development Team forecasts functionality to be developed
Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering them. It makes visible all of the work that the Development Team identifies as necessary to meet the Sprint Goal.
- Includes detailed plan for delivering increment
- Updated throughout the Sprint as more is learned
- Only the Development Team can change it during a Sprint
- Includes at least one high-priority process improvement
- Tracked daily to project the likelihood of achieving Sprint Goal
Sprint
The Sprint is the heart of Scrum, a time-box of one month or less during which a "Done", useable, and potentially releasable product Increment is created.
- Fixed length (usually 2-4 weeks)
- New Sprint starts immediately after the conclusion of the previous Sprint
- Contains all development work, plus Sprint Planning, Daily Scrums, Sprint Review, and Retrospective
- No changes are made that would endanger the Sprint Goal
- Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned
Daily Scrum
The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.
- Held at the same time and place each day
- Team members explain what they did yesterday, will do today, and any impediments
- Optimizes team collaboration and performance
- Identifies and removes obstacles to progress
- Promotes quick decision-making and improves team's level of knowledge
Sprint Review
The Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. The Scrum Team and stakeholders collaborate about what was done in the Sprint.
- Four-hour time limit for one-month Sprints
- Demonstrates completed work to stakeholders
- Product Owner explains what has and hasn't been done
- Team discusses what went well and problems encountered
- Group collaborates on what to do next to optimize value
Sprint Retrospective
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
- Three-hour time limit for one-month Sprints
- Inspects how the last Sprint went regarding people, relationships, process, and tools
- Identifies and orders major items that went well
- Creates plan for implementing improvements
- Adapts the definition of "Done" as needed
Increment
The Increment is the sum of all the Product Backlog items completed during a Sprint and all previous Sprints. At the end of a Sprint, the new Increment must be "Done".
- Must be in useable condition regardless of whether the Product Owner decides to release it
- Contains all previously delivered increments
- Must meet the Scrum Team's definition of "Done"
- Represents a step toward a vision or goal
- Must be usable regardless of whether the Product Owner decides to actually release it