Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.
Explanation
The Sprint Backlog is created during Sprint Planning and is owned by the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint. It includes the selected Product Backlog items, the plan for delivering them (typically decomposed into tasks), and the Sprint Goal.
The Sprint Goal is the commitment associated with the Sprint Backlog. It provides coherence and focus, giving the Developers flexibility in exactly what they build while maintaining a clear objective. If the work turns out to be different from what was expected, the Developers negotiate the scope with the Product Owner without affecting the Sprint Goal.
The Sprint Backlog is updated throughout the Sprint as the Developers learn more. As new work is identified, the Developers add it. As work becomes unnecessary, they remove it. Only the Developers can change the Sprint Backlog during the Sprint.
Key Points
- •Composed of selected backlog items, the delivery plan, and the Sprint Goal
- •Owned and updated exclusively by the Developers during the Sprint
- •Updated in real-time as the team learns and adapts
- •The Sprint Goal is the commitment that provides coherence
Exam Tip
Only the Developers can modify the Sprint Backlog during the Sprint. The Product Owner cannot add items without the Developers' agreement.
Frequently Asked Questions
Related Topics
Sprint Planning
Sprint Planning is the Scrum event that initiates each Sprint by defining the Sprint Goal, selecting Product Backlog items to work on, and creating an actionable plan for delivering the Increment.
Product Backlog
The Product Backlog is an emergent, ordered list of everything that might be needed in the product, serving as the single source of requirements for any changes to be made.
Daily Standup (Daily Scrum)
The Daily Scrum (also called Daily Standup) is a 15-minute timeboxed event held each day of the Sprint where Developers inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Sprint Review
The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.
Timeboxing
Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.
Resource Leveling
Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Cost Performance Index (CPI)
Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.
Schedule Performance Index (SPI)
Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.
Part of
Agile & Hybrid
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.