The say do ratio is the share of committed sprint work a team actually finishes by the end of the sprint. On LinkedIn the same problem keeps coming back under other names: “sprint spillover”, “carryover”, “rollover”. Allen Holub has argued there is no such thing as a sprint “spillover”, and Stephanie Ockerman has asked teams to stop talking about “carryover” at all. Whatever you call it, the question underneath is the same: how often does the team do what it said it would do at sprint planning, and how do you raise that number without padding estimates?
How to calculate the say do ratio
The basic formula is simple:
Say do ratio = work completed from the sprint commitment ÷ work committed at sprint planning
You can count story points, issue count, or hours. Pick one unit and keep it. Two details decide whether the number is honest:
- Use the planning-day snapshot. If work added mid-sprint is counted in the denominator, the figure turns into a completion rate, not a measure of kept commitments. Record the committed scope when the sprint starts.
- Use the original estimate. If stories are re-estimated during the sprint, the ratio moves for reasons unrelated to delivery. Freeze the estimate used at planning.
An illustration, not customer data: a team commits 40 points at planning and finishes 30 of them. Its say do ratio is 75%. Five more points were added mid-sprint and finished; they are reported separately as unplanned work, not added to either side.
What a “good” say do ratio looks like
There is no industry standard. Treat the trend as more important than the level. A ratio that swings between 50% and 100% tells stakeholders nothing about the next sprint; a ratio that sits steadily in a narrow band lets a product owner and a release manager plan around it. A permanent 100% is also a warning sign: it usually means the team commits to less than it can do.
Why the say do ratio drops
- Planning on velocity alone. Last sprint’s average is pulled in without subtracting this sprint’s time off, public holidays, support rotation or training.
- Uneven load. The team total fits, but one specialist holds twice their available hours.
- Unready stories. Items enter the sprint unsliced or without acceptance criteria.
- Unreserved interrupts. Production issues consume capacity that was never set aside.
All four are planning problems. That is why the say do ratio belongs in sprint planning, not only in the retrospective. Our Sprint Planning Guide covers the full process, and over-commitment is the first item on our list of common sprint planning mistakes.
Five steps to raise it
- Start from capacity, then check velocity. Calculate each person’s available hours for this sprint first. Velocity tells you what is typical; capacity tells you what fits. See story points vs hours for how the two units work together.
- Check load per person, not only per team. A team total that fits can still hide an overloaded individual.
- Reserve a buffer for unplanned work. Base it on the last few sprints of interrupts, not on a guess.
- Gate the sprint with a definition of ready. Use the sprint planning checklist before anything is committed.
- Commit to a goal, forecast the items. A clear sprint goal lets the team trade scope mid-sprint without breaking the commitment that matters.
Doing this in Jira with Divim
Jira’s sprint report lists issues not completed when a sprint closes, but it does not show whether the sprint was overloaded on planning day. 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 over-commitment is visible during planning instead of at the sprint review. When unfinished items return to the backlog, Backlog Refinement for Jira helps the team re-size and re-order them before the next planning session.
Key takeaways
- The say do ratio is committed work completed divided by work committed at sprint planning.
- Use the planning-day scope and the original estimates, or the number stops measuring commitments.
- A stable ratio matters more than a high one; a constant 100% often means under-commitment.
- Raise it at sprint planning: plan to real capacity per person, reserve for interrupts, and gate on readiness.
FAQ
Is the say do ratio the same as sprint completion rate?
No. Completion rate usually includes work added during the sprint. The say do ratio only measures the scope committed at sprint planning.
Should the say do ratio be used to compare teams?
No. Teams estimate differently, and a target imposed from outside invites padded estimates. Use it within one team, over time, to improve planning.
Commit to what fits. Try Sprint Planning, Capacity & Resource Planning free on the Atlassian Marketplace, and read the full Sprint Planning Guide.




Leave a Reply
Your email is safe with us.