Agile and the IT budget
Fund teams · Forecasting · Staffing · What to ask for · In government · Talk to us · Sources
Annual budgets assume you know the scope a year ahead. Agile teams assume you’ll learn as you go. Here is how leading organizations fund, forecast and staff technology work so both can be true.
The quotes and sources could not be loaded. Please reload the page.
Fund teams and value streams, not projects
The Scaled Agile Framework’s Lean Budgets approach funds value streams instead of projects, governed by guardrails. It lists the problems with project funding: slow approvals, premature decisions, temporary teams, rigid plans and constant re-budgeting.
The Beyond Budgeting principles point the same way: directional, relative targets; lean, unbiased forecasts; resources made available as needed rather than through detailed annual allocations; and coordination by business rhythms rather than the calendar year.
The shift is from approving a fixed scope up front to funding a stable team and steering what it works on every few weeks.
Forecasting without fixed scope
Use measured throughput
Forecast from what the team actually finishes: throughput (items finished per unit of time) and cycle time (elapsed time from start to finish).
Plan in increments
Plan in increments of 8 to 12 weeks, the length of a SAFe Planning Interval, rather than a year at once.
Re-forecast each increment
At the end of every increment, update the forecast with what the team actually delivered.
The US Government Accountability Office adapts its cost-estimating process to Agile: estimates should reflect the backlog and use historical data, and story points are not a consistent measure of cost.
Staffing
Agile favors stable, long-lived teams. A Scrum team is typically 10 or fewer people.
What does a team cost?
The calculator needs JavaScript. In words: 5 developers × $134,040 median pay × a loaded-cost multiplier of 1.3 = $871,260 per year (illustrative).
Illustrative. Median pay from the US Bureau of Labor Statistics; your local costs will differ. The loaded-cost multiplier (benefits, equipment, overhead) is an assumption you can change.
The median pay used here is $134,040 a year for software developers, QA analysts and testers (May 2025). The US Bureau of Labor Statistics projects 10% growth in these jobs from 2025 to 2035.
What to ask for instead of a Gantt chart
- A product goal for the year and an ordered backlog that you can see.
- Delivery every few weeks you can try, not a status report.
- The four DORA delivery metrics, trended monthly.
- SLOs for the services the business depends on, signed off by the business.
- A forecast range from real throughput, updated every planning increment.
- A security standard the pipeline is measured against.
Follow a team from backlog to production in the Agile delivery playbook →
In government
- The GAO’s Agile Assessment Guide (GAO-24-105506, issued November 2023) is written for federal auditors and agencies.
- “Since 2012, OMB has required investments to deliver functionality every 6 months.”
- 18F worked with California and Mississippi on modular contracting combined with Agile to replace legacy systems, delivering value in months rather than years.
- Texas agencies using adaptive project methods such as Agile grew 9% compared with 2020.
Public bodies can buy and fund Agile work; the guidance already exists.
Want a second opinion on how your technology work is funded and measured?
Tell us how you plan and budget today.
This request form needs JavaScript. Please use the contact page instead.
Sources
Facts checked Oct 12, 2026.
Illustrative simulation. The organization, team and numbers are invented to explain the ideas and are not measured data or a benchmark. Framework names belong to their owners; King Tech is independent and isn't affiliated with them.