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.
Know it well enough for the exam? Questions on Sprint Backlog are scenario-based, not definitional.
Practice it freeExplanation
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 ordered list of everything that is known to be needed in the product, serving as the single source of requirements and the primary artifact for managing scope in agile projects.
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 plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
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 that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Power Interest Grid (Power/Influence Grid)
The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.
Part of
Agile & Hybrid
Practice Sprint Backlog
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.