The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), and an actionable plan for delivering the Increment (how). It is a plan by and for the Developers — a highly visible, real-time picture of the work they plan to accomplish to achieve the Sprint Goal. It is updated throughout the Sprint as more is learned, and because it belongs to the Developers, they alone add, remove or re-plan items within it during the Sprint.

The commitment for the Sprint Backlog is the Sprint Goal: the single objective for the Sprint. Although it is a commitment by the Developers, it provides flexibility in the exact work needed to achieve it, and it creates coherence and focus so the team works together rather than on separate initiatives. The Sprint Goal is created during Sprint Planning. If the work turns out different than expected, the Developers collaborate with the Product Owner to renegotiate the scope of the Sprint Backlog within the Sprint — without affecting the Sprint Goal.

Exam tip: Sprint Backlog = Sprint Goal + selected items + plan, owned only by the Developers, updated continuously. Its commitment is the Sprint Goal, which stays stable even when scope is renegotiated.

📥 Plan for the Sprint🛠️ Developer-owned🔄 Real-time🎯 Sprint Goal

🔁 Professional Scrum Master (PSM)