The sprint goal was clear: “Customers can reset their own password without contacting support.” The team met it. The next sprint’s goal was also met, and so were the two after that. In the retrospective nobody had a complaint.
Then the release manager looked at the date the team had committed to for 12 June. It was no longer realistic. Every sprint had succeeded, and the release had still moved.
What a sprint goal is for
A sprint goal is the single objective a Scrum team commits to for one sprint. It gives the sprint a purpose and lets the team adjust the work inside the sprint while the goal stays fixed. It is set at sprint planning, and it reflects the team’s expert engineering judgment about what can be achieved in the next two weeks. That judgment is worth protecting, and the goal protects it well.
Two weeks is a short horizon
The release date was committed by a different vote, a confidence vote taken at planning, and it spans many sprints. After that vote, three things quietly move it: the three things that erode a committed release date are scope creep, dependencies surfaced too late, and capacity changes.
None of them needs a missed sprint goal. Scope can be added to the Fix Version at backlog refinement, between sprints. A dependency on another team can surface in a sprint whose goal it does not touch. A teammate can be moved to another project for three weeks, and the remaining team can still meet each goal by choosing smaller ones. The sprint goal measures the sprint. It was never built to measure the release.
Give the release a goal of its own, and keep it live
The answer is not to replace the sprint goal. It is to treat the committed date as a commitment with a live confidence band, and to read it each time you set the sprint goal.
- Write the committed date and the confidence it was committed at (P50, P85 or P95) beside the release goal.
- Point the release at one Fix Version, so scope has a boundary.
- Choose a throughput window long enough to include the team’s normal mix of support work and interruptions.
- Record known time off per person, and import public holidays per team, before they arrive.
- At sprint planning, after the sprint goal is set, read the gap in days between the committed date and the forecast at the committed confidence.
- Treat amber as a prompt to renegotiate, not as a failure.
An illustration, not customer data. A release is committed for 12 June at 85% confidence. At the vote the 50% forecast sits at 2 June and the 85% forecast at 11 June: one day of margin. Over four sprints the team meets every sprint goal. In the same weeks, nine issues are added to the Fix Version at refinement, a hard dependency on another team’s API is found, and one engineer is moved to half-time elsewhere. No one did anything careless. The 50% forecast is now 9 June and the 85% forecast is 22 June, ten days past the commitment. The date sits between P50 and P85, so it reads amber, and the sprint board still reads green.
Now the conversation has a number on it, and it happens five weeks before the release, not the week of it. Ask the other team for the API earlier? Move a Should-have to the next release? Or move the date while everyone who depends on it can still re-plan? Every option is the team’s call. What changes is when the call is made.
Where Advanced Release Planning fits
Advanced Release Planning for Jira does not set sprint goals and does not replace them. It supplies the figure the sprint board is missing. It reads the Fix Version, the Jira issue links, the throughput window you choose, and the Capacity Awareness settings for time off and public holidays. It re-runs the Monte Carlo forecast as those change and reports the committed date against the 50%, 85% and 95% bands, with the gap in days attributed to scope, dependencies or capacity. The team sets the assumptions: which throughput window, whose capacity, what is in scope. The app does the arithmetic at Monte Carlo scale and keeps it current. Green at or above P85, amber between P50 and P85, red below P50.
For why a sprint-level chart cannot stand in for this, see why the velocity chart reports last sprint, but the committed date needs the next ten. For the fixed-length version of the same problem, see why timeboxing fixes the date but not what fits inside it. For exactly what the app reads, see the sprint goal reference doc.
Key takeaways
- A sprint goal commits the team to one objective for one sprint, and it reflects expert engineering judgment.
- A committed release date spans many sprints, and meeting each sprint goal does not show whether it still holds.
- Scope creep, late dependencies and capacity changes move the date between and around sprints.
- Read the gap in days between the committed date and the forecast every time you set the sprint goal.
FAQ
What is a sprint goal?
The single objective a Scrum team commits to for one sprint. It is set at sprint planning and gives the sprint a purpose while the team adjusts the work inside it.
What is the difference between a sprint goal and a release date?
A sprint goal covers one sprint. A committed release date covers many, and it comes from a confidence vote. Both are commitments, but only the release date is exposed to scope creep, late dependencies and capacity changes between sprints.
How do I know the release date still holds if every sprint goal is met?
Compare the current forecast at the confidence the date was committed at with the date itself. The gap in days, and whether it reads green, amber or red, tells you.
Protect the sprint. Protect the date too. See the committed date and its live confidence band in Advanced Release Planning, or start a free trial on the Atlassian Marketplace.




Leave a Reply
Your email is safe with us.