Can a Scrum team have multiple sprint goals? On LinkedIn, Michael Lloyd’s post “Scrum without a single sprint goal is not Scrum” and Stephen Angood’s “No sprint goal? You’re not doing Scrum” drew long comment threads from teams that run two or three goals per sprint, or none. This article answers the question directly, explains why teams drift into several goals, and shows how to get back to one at sprint planning.
What the Scrum Guide says
The 2020 Scrum Guide describes the Sprint Goal as “the single objective for the Sprint”. It is the commitment attached to the Sprint Backlog, it is created during sprint planning, and it gives the team flexibility in the exact work needed to reach it. So the short answer is no: in Scrum, a sprint has one goal. The selected backlog items are a forecast; the goal is the commitment.
Why teams end up with multiple sprint goals
- Several stakeholders, one team. Each stakeholder wants their item named as a goal.
- The team is really two teams. Sub-groups work on unrelated products and share only a board.
- Goals are written as ticket lists. “Finish ABC-12, ABC-15 and ABC-19” is three tasks, not a goal.
- Keeping the lights on. Support and maintenance work is named as a goal so it feels visible.
What multiple sprint goals cost
A single goal tells the team what to protect when something goes wrong mid-sprint. With three goals, there is no rule for which one gives way, so the team either works overtime or drops whatever is least visible. Focus is split, the sprint review becomes a status report, and the team’s commitment becomes hard to read. Missing goals also shows up as unfinished work, which is one of the common sprint planning mistakes.
How to turn several goals into one
- Find the common outcome. Ask what the candidate goals have in common for the user or the product. Often two “goals” serve one outcome.
- Rank, then pick. If they share nothing, the product owner chooses the one that matters most this sprint. The others remain backlog items in the forecast, not goals.
- Reserve capacity for run work. Keep support and maintenance as a planned capacity allocation rather than a goal.
- Check that the goal fits capacity. A goal the team cannot reach with the hours it actually has this sprint is not a commitment.
- If sub-teams never share an outcome, split the team. Two products usually need two backlogs and two goals in two sprints.
For wording, see How to Write a Sprint Goal. For where the goal sits in the meeting, see the sprint planning meeting agenda, and for the full process, the Sprint Planning Guide.
Doing this in Jira with Divim
Teams often hold several goals because they cannot see whether one well-scoped goal would fit. Divim’s Sprint Planning, Capacity & Resource Planning for Jira puts each team member’s available capacity, minus days off and other commitments, next to the work assigned to them, so the team can check during planning whether the goal and its forecast fit. Backlog Refinement for Jira helps the team re-size and re-order the items that did not make the goal, so they are ready for the next sprint.
Key takeaways
- The Scrum Guide defines one Sprint Goal per sprint; backlog items are the forecast.
- Multiple sprint goals split focus and remove the rule for what to protect mid-sprint.
- Combine goals into a shared outcome, or rank and pick one; keep run work as a capacity allocation.
- A team that never shares a goal may need to become two teams.
FAQ
Can a sprint goal have several parts?
Yes, if the parts serve one outcome. “New users can sign up and verify their email” is one goal with two steps. “Fix billing bugs and launch the new dashboard” is two goals.
What if the product owner insists on multiple sprint goals?
Ask which one wins if both cannot be met. The answer is the sprint goal; the rest is forecast.
One goal, sized to real capacity. Try Sprint Planning, Capacity & Resource Planning free on the Atlassian Marketplace, and read the Sprint Planning Guide.




Leave a Reply
Your email is safe with us.