Definition
A sprint goal is a single, concise objective that the Scrum team commits to achieving during a sprint. It is crafted during sprint planning and provides coherence to the set of backlog items selected for the sprint. Rather than treating the sprint as a random collection of tickets, the sprint goal gives the team a unified purpose.
The Scrum Guide describes the sprint goal as a "commitment" for the Sprint Backlog, similar to how the Definition of Done is the commitment for the Increment. It is negotiable in terms of scope (the team can adjust which stories to include) but non-negotiable in terms of intent (the desired outcome should remain constant throughout the sprint).
Sprint goals serve as a decision-making filter during the sprint. When a developer finishes their current task and needs to decide what to pick up next, the sprint goal tells them which backlog item has the highest priority. When a stakeholder requests an urgent change mid-sprint, the team can evaluate it against the sprint goal: does this help achieve the goal, or does it threaten it?
Why It Matters for Product Managers
Sprint goals transform sprint planning from a capacity-filling exercise into a strategic conversation. Without a goal, planning often devolves into "how many story points can we fit?" With a goal, planning starts with "what outcome do we need this sprint?" and works backward to select the right items.
For PMs, sprint goals are also a communication tool. When your manager asks what the team is working on this sprint, you can give a crisp, one-sentence answer instead of listing 12 Jira tickets. This is especially valuable when managing multiple stakeholders who care about different aspects of the product. Connect your sprint goals to your OKRs so that every sprint visibly advances a quarterly objective.
How to Apply It
- ☐ Write the sprint goal during sprint planning before selecting individual backlog items
- ☐ Keep it to one sentence (two at most) that describes the outcome, not the tasks
- ☐ Make it demo-able: you should be able to show progress toward the goal at the sprint review
- ☐ Post the sprint goal visibly (Slack channel topic, Jira board header, team wiki)
- ☐ Reference the sprint goal in daily standups when prioritizing work
- ☐ Track sprint goal achievement rate over time (aim for 80%+ achievement across sprints)
- ☐ Map each sprint goal to a quarterly OKR or product roadmap initiative
For help connecting sprint goals to broader product strategy, the guide on building a product roadmap covers how to decompose quarterly goals into sprint-sized increments.