There is a conversation that almost no agile transformation dares to have. It is not about the framework chosen, nor about whether the teams do the daily well, nor about whether the product owner has enough authority. It is a conversation about money. About how it is decided what gets funded, when, and on what criteria. About whether the organization's financial model—built in many cases decades ago and barely questioned since—is compatible with the way we want to work. This question is uncomfortable because it touches power structures that go far beyond agile teams. But ignoring it has a cost that, sooner or later, becomes visible.
There is a pattern that repeats in many agile transformations of a certain size. Teams learn to iterate, to deliver value in short cycles, to adapt when the context changes. They do it reasonably well. And yet, at some point in the organization, someone has to approve a budget. And that budget was negotiated six months ago, with information that no longer exists, for a plan the market has already made obsolete.
What happens next is predictable: the agile team adapts within the margins it is given, but those margins are defined by a financial structure that has not changed. The important decisions (what gets built, how much is invested, what gets cancelled) still depend on annual planning cycles designed for a stable environment that no longer exists.
This is not a problem of team mindset. It is a systemic problem. And like any systemic problem, it is not solved with more training.
Why the annual budget and agility are incompatible
The traditional annual budget was designed for a radically different context from today's. Jeremy Hope and Robin Fraser in Beyond Budgeting (2003) documented in detail how this model—developed in the first half of the 20th century—generates a series of dysfunctions that are precisely the opposite of what agility seeks to build.
The annual budget forces high-precision decisions about the future with minimal available information. It requires building detailed business cases before knowing almost anything about whether the solution makes sense. It creates perverse incentives: teams learn to ask for more than they need so they can negotiate downward, and to spend everything before the year ends so they do not lose the next year's budget. And above all, it makes the financial decision pace incompatible with the learning pace of a team that delivers every two weeks.
McKinsey documented in an analysis on agile funding that, in organizations with traditional planning processes, up to 50% of the budget ends up being absorbed by unplanned or low-priority work, precisely because the initial plan was made with incorrect information and the system has no agile mechanisms to correct course. The same analysis noted that organizations that had adopted agile funding practices were able to react up to twice as fast to changes in context during the 2020 pandemic.
Funding projects vs. funding value
The project-based funding model has an apparently reasonable logic: you define what you want to build, estimate the cost, approve the budget, execute, and measure whether you have delivered. The problem is that this logic assumes you know what you want to build before you start building it, that the estimated cost has some relation to reality, and that following the plan is equivalent to delivering value. None of these three assumptions is reliable in complex environments.
Scaled Agile Framework (SAFe) introduced the concept of Lean Budgets to address this contradiction: instead of funding temporary projects with teams assembled and disbanded for each initiative, the flow of value is funded continuously. Budgets are allocated to value streams with guardrails that allow some flexibility within agreed limits. The teams persist; the work changes.
Beyond budgeting: an alternative with history
The Beyond Budgeting movement has for more than two decades documented organizations that have abandoned the traditional annual budget and built alternative models based on decentralization, continuous adaptation, and trust.
Bjarte Bogsnes, author of Implementing Beyond Budgeting (2016), led the elimination of the annual budget in two large European companies and has extensively documented what happens when an organization decides to manage its resources in a radically different way.
What Beyond Budgeting proposes is not to eliminate financial control, but to separate three processes that the traditional annual budget mixes in a not very useful way: target setting, forecasting, and resource allocation. By treating them as independent processes—with different rhythms, owners, and logics—organizations gain adaptive capacity without losing financial rigor.
The real problem is not technical, it is political
It would be convenient to think that the obstacle to changing the funding model is technical: lack of tools, adequate metrics, or clear processes. But anyone who has tried to have this conversation in a real organization knows that the obstacle is mainly political.
The annual budget is not just a mechanism of financial control. It is also a mechanism of power. It defines who can approve what, at what level of the hierarchy decisions are made, and who has visibility over what. Changing the funding model inevitably implies redistributing power. And that generates resistance (not always explicit, but always present).
McKinsey pointed this out clearly in its analysis on agile funding: the greatest obstacle to the transition is not the technical complexity of the new model, but the willingness of senior leaders to commit to change and to give up part of the centralized control that the annual budget gave them. Without that commitment, changes to the funding model remain superficial adjustments that do not alter the underlying logic.
This does not mean the problem is unsolvable. It means it requires a different conversation, involving different people, and that it has to be framed in terms that the CFO and the management committee can recognize as their own: efficiency in resource allocation, reduction of opportunity cost, improvement in responsiveness to the market. Not in terms of agile frameworks.
Where to start without throwing the system out the window?
The good news is that changing the funding model does not require a revolution. Thoughtworks published in 2025 a practical analysis on how to transition from project-based funding toward more product-oriented models without dismantling existing financial processes. Some of its recommendations are applicable even in organizations with very conservative financial structures.
According to this analysis:
- First step: introduce more frequent review cycles within it. If the annual budget exists and is not going to disappear, at least it should include quarterly reviews with real capacity for reallocation. This does not eliminate the rigidity of the system, but it reduces it.
- Second step: identify a specific product or value stream where to experiment with a different funding model. Continuous funding of a stable team, instead of funding successive projects, makes it possible to demonstrate the impact of the change with real data before scaling it.
- Third step: involve finance from the beginning, not as recipients of a change that others have designed, but as co-designers of the new model. The experience of organizations that have taken this path consistently suggests that the most productive conversations happen when the agile team and the finance team sit down together to explore the problem, without either arriving with the solution already made.
And what does this mean for agile teams?
It is important to be honest about the limits of individual action here. If you work on an agile team in an organization with a rigid annual funding model, you probably cannot change it alone. This is, to a large extent, a systemic problem that requires decisions several levels above most agile practitioners.
What you can do is name it. Make visible the contradiction between the work rhythm you are trying to build and the financial decision rhythm around you. Provide the language—value, flow, adaptation, opportunity cost—that makes it possible to have that conversation in terms that resonate beyond the agile community. And look for allies in finance, because there are CFOs who have spent years frustrated with the annual budget for reasons completely independent of agility.
Can an organization not be truly agile if its funding model still operates with last century's logic? It can be more agile than before. It can improve a great deal. But at some point along the way, the annual budget becomes the ceiling.
If this question resonates with you and you want to hear the experience of someone who has tried to cross that line in a real organization, on March 19 Antonio Lorente will share in the online meetup *Fck the Budget (pero con cariño)**, organized by Agile Spain, what he found on the other side.
References
- Hope, J. and Fraser, R. (2003). Beyond Budgeting: How Managers Can Break Free from the Annual Performance Trap. Harvard Business Press.
- Bogsnes, B. (2016). Implementing Beyond Budgeting: Unlocking the Performance Potential (2nd ed.). Wiley.
- Scaled Agile, Inc.
- (2025). Lean Budgets. Scaled Agile Framework. https://framework.scaledagile.com/lean-budgets
- (2025). Transitioning to Value Stream Funding Competency. Scaled Agile Framework. https://framework.scaledagile.com/lean-portfolio-management-discipline/transitioning-to-value-stream-funding-competency/
- McKinsey & Company. (2022). "Agile funding: An investment management approach to funding outcomes". McKinsey Digital.
- Deloitte UK. (2026). "Moving beyond budgets: how agile funding is a necessity for tech success". Deloitte Consulting Blog.
- Thoughtworks. (2025). "Funding agility: Moving beyond project budgets". Thoughtworks Insights.
- Digital.ai. (2026). "18th Annual State of Agile Report". Digital.ai.
Comments (0)
Log in to your Scrum Manager area to comment