What is the Sprint Goal
The Sprint Goal is the single objective for the Sprint. It is the commitment for the Sprint Backlog.
The Sprint Goal is created during Sprint Planning. It gives the team a shared "why" for the Sprint. The selected Product Backlog items provide the "what."
Why It Matters
Teams that work from a Sprint Goal stay focused. Teams that work from a list of items often deliver scattered work that does not add up to anything.
The Sprint Goal also lets the team and Product Owner negotiate scope during the Sprint. New information can shift which items get delivered, as long as the Sprint Goal is met. Without a Sprint Goal, every change feels like a broken commitment.
How It Works in Scrum
The Sprint Goal is created in Sprint Planning. The Product Owner proposes how the product can increase its value. The team shapes that into a Sprint Goal.
A good Sprint Goal:
- Is a single, clear objective
- Connects to the Product Goal
- Helps the team make trade-offs
- Means something to stakeholders
- Can be completed in the Sprint
During the Sprint, the Sprint Goal does not change. Scope can flex. If the Sprint Goal becomes obsolete, the Product Owner can cancel the Sprint.
The Sprint Goal is the focus of the Daily Scrum.
Common Mistakes
- No Sprint Goal at all. Scope cuts feel like failures because there is no goal to anchor them.
- A Sprint Goal that is just a list of work. "Complete tickets ABC-101 through ABC-115" is not a goal.
- A Sprint Goal nobody outside the team understands. Too internal to guide stakeholders.
- Changing the Sprint Goal mid-Sprint. If the goal must change, cancel the Sprint and start a new one.
- Vague goals that do not guide decisions. "Improve the product" is not a goal.
Key Takeaways
- The Sprint Goal is the single objective for the Sprint.
- It lets the team negotiate scope without breaking commitment.
- A good Sprint Goal connects to the Product Goal and is clear to stakeholders.
- The Sprint Goal is the focus of the Daily Scrum.