To report sprint predictability to non-technical government leadership, replace velocity jargon with three numbers they already trust: your say/do ratio (the share of committed work the team actually finishes), the trend across the last several sprints, and a plain date-and-budget forecast built from real capacity. Lead with reliability, show the direction of travel, and keep the decision trail behind every commitment.

Why predictability — not velocity — is what leadership wants to hear

A deputy program manager prepping for a quarterly portfolio review does not want a burndown chart. She wants to answer one question from the agency CIO: “Will this be done by the end of the fiscal year, and can I stake my name on the date?” When her scrum master sends over a slide full of story points and sprint velocity, the translation work lands on her desk — and a number she cannot explain is a number she will not repeat up the chain.

This gap is wider in government than in most commercial settings. Public-sector leaders answer to appropriators, inspectors general, and oversight committees. They report against obligated funds and statutory deadlines, not engineering throughput. And with workforce reductions and flat budgets now the norm across federal, state, and local agencies, the pressure to deliver the same mission with fewer people makes a credible delivery forecast more valuable, not less. The job of a good sprint report is to convert what the team knows into something leadership can defend.

How do you report sprint predictability to leadership?

Use a five-part framework that turns the team’s working data into one page a non-technical leader can read in two minutes.

1. Lead with the say/do ratio, not raw velocity. Velocity tells leaders how fast a team moves; predictability tells them whether the team does what it said it would. Report committed-versus-completed work as a percentage — “the team finished 90% of what it committed to this sprint.” That single ratio is intuitive to anyone who has ever made a promise and kept it.
2. Show a trend, never a snapshot. One sprint is noise. Report a rolling average across the last four to six sprints so leadership sees direction, not a single data point. A say/do ratio holding steady at 88–92% is the story of a reliable team; a ratio swinging from 60% to 110% tells the story of a team that does not yet understand its own capacity.
3. Translate the forecast into a date and a dollar boundary. Leadership thinks in fiscal-year ends, option-year exercises, and obligation deadlines. Take the remaining scope, divide by the team’s reliable delivery rate, and convert sprints into a calendar date. Then state plainly whether that date lands inside or outside the fiscal-year window.
4. Attach the decision trail. For every commitment, be ready to show why the team committed to that number: who was allocated, which days off and holidays were subtracted, and what the capacity math produced. This is the difference between “trust us” and “here is the record.” In a climate where auditors and oversight increasingly ask agencies to prove what happened, who acted, and what evidence supports a decision, a documented capacity-and-commitment trail is a quiet asset.
5. Keep it to one page. A non-technical leader should be able to read the report in under two minutes: the reliability number, the trend, the forecast date, and one line on risk. Detail lives in the backlog for anyone who wants to drill in.

A worked example

Suppose a six-person agency team runs two-week sprints. Over the last six sprints they committed to 40, 38, 42, 39, 41, and 40 points and completed 36, 35, 38, 37, 36, and 38. The average say/do ratio is about 91% — reliable. Their dependable delivery rate is roughly 36 points per sprint (using completed, not committed, work). With 180 points of scope remaining for a fiscal-year release, the forecast is 180 ÷ 36 = 5 sprints, or about 10 weeks. If the team is reporting in early July and the fiscal year ends September 30, that forecast lands with roughly two weeks of buffer — a green light leadership can defend, with a clear note that any scope added beyond 180 points moves the date.

Notice the slide says nothing about story points: it says “the team reliably delivers about 91% of what it commits to, the trend is steady, and current scope finishes about two weeks before fiscal year-end.”

Making the report repeatable inside Jira

These reports are usually painful because the inputs live in three places — velocity in one tool, the team’s leave calendar in another, and the commitment rationale in someone’s memory. Pulling capacity, allocation, days-off, and past velocity onto one screen in the Jira backlog — before the team commits — means the numbers that drove the sprint plan are the same numbers you report afterward. Sprint planning with Capacity Planning for Jira does exactly that: it plans sprints and team capacity together on one screen using past velocity, days off, and allocation, so the commitment and its rationale are recorded in the same place the work lives. As agencies modernize onto Atlassian Cloud and Atlassian Government Cloud (AGC), doing planning and reporting in one Cloud Fortified app — running on Atlassian’s SOC 2 Type II / ISO 27001 platform — removes the spreadsheet reconciliation step that makes most predictability reports late and brittle.

FAQ

What is a good say/do ratio for a government agile team? There is no universal target, but most reliable teams settle into a steady 80–95% band. The exact number matters less than consistency — a stable ratio is more defensible to leadership than an occasionally perfect one.

Should I report velocity to non-technical leadership at all? Generally no. Use velocity internally to build the forecast, then report the forecast as a date and a reliability percentage. Leaders rarely need the underlying point math, but keep it ready in case they ask.

How often should predictability go up the chain? Match leadership’s cadence — usually monthly or per portfolio review — even though the team measures every sprint. Report the trend, not every individual sprint result.

---

Try it: Install free · Help docs