Skip to content
PMPCAPM

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

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.