An organisation can deliver software every two weeks and still take six months to move money, stop a low-value initiative or change an enterprise priority.
This is one of the central contradictions in large-scale agility.
Teams become faster. Work is broken into smaller increments. Product owners continuously reprioritise backlogs. Technology delivery becomes more responsive. Yet capital remains tied to annual projects, governance reviews remain calendar-driven, portfolio metrics remain baseline-focused and strategic decisions still require long approval chains.
The organisation becomes agile at the edge and rigid at the centre.
That gap matters because enterprise value does not come from sprint velocity. It comes from moving scarce resources toward changing priorities fast enough to matter.
The Strategic Context
The supplied Deloitte 2020 point of view argues that Agile and project portfolio management are not inherently contradictory. It describes PPM as a closed-loop system involving demand, project/program, results and portfolio management, and notes that core management concerns remain relevant regardless of delivery method.
The important change appears as Agile scales.
Deloitte identifies value streams and epics as concepts that need to connect to demand and portfolio management. It also notes that scaled Agile organisations may fund value streams, decentralise some financial decisions and continuously reprioritise work. If portfolio mechanisms do not adapt, the linkage between portfolio-level decisions and team-level delivery can break.
The Week 11 Study Notes add an important distinction: agility in complex portfolio and program environments means responsiveness to changing conditions. It should not be reduced to the adoption of a particular Agile framework.
Together, these sources support a wider executive conclusion. Strategic agility is an organisational decision capability, not a delivery methodology.
What Leaders Commonly Misread
The first misread is to treat Agile adoption as a technology-team transformation. If business priorities, funding, governance and operating-model decisions remain unchanged, local speed may simply create more output against stale priorities.
The second is to assume that continuous delivery eliminates the need for portfolio management. The opposite is true. When teams can change direction quickly, enterprise leaders need stronger clarity about strategic intent, funding boundaries and cross-portfolio trade-offs.
The third is to continue measuring adaptive work only against fixed scope. Deloitte notes that traditional red-amber-green control commonly compares actual performance with predetermined scope, budget and timeline. Agile work requires analogous portfolio-level health measures that reflect flow, value and evolving priorities without abandoning financial discipline.
The fourth is to decentralise decisions without redefining accountability. Delegated authority should speed local choices inside clear strategic and financial boundaries. Without those boundaries, decentralisation can become fragmented investment.
The fifth is to keep funding projects while asking teams to behave like persistent products or value streams. The organisational unit of funding shapes behaviour. If money, authority and metrics are tied to temporary projects while teams are expected to optimise long-lived customer value, governance sends conflicting signals.
Reframing the Issue
The real question is not "Are we Agile?" It is:
How quickly can the enterprise translate new information into a different allocation of attention, money and capacity?
A strategically agile portfolio needs four connected capabilities.
Strategic sensing
The organisation detects changes in customers, competitors, regulation, technology, operating performance and delivery evidence.
Portfolio interpretation
Leaders determine whether those signals materially change strategic priorities or business cases.
Resource mobility
Funding and scarce capabilities can move without waiting for an annual reset.
Delivery adaptability
Teams can change scope or sequencing without destroying enterprise control.
If any one layer is slow, overall agility is constrained.
Related article: Strategy Changes. The Portfolio Must Change With It.
Value Streams Change the Portfolio Conversation
Deloitte defines value streams in its PPM context as ecosystems of teams that deliver against large cross-cutting initiatives such as epics. The strategic relevance is that work is organised around value creation rather than only around temporary project structures.
This can improve continuity. Teams retain domain knowledge, customer understanding and technical ownership. Funding can be allocated to a value-producing capability rather than repeatedly reassembled around project boundaries.
But value-stream funding is not automatically superior. Persistent structures can also protect low-value work if governance becomes too permissive. Leaders still need explicit investment hypotheses, performance evidence and stop decisions.
The important principle is alignment between:
- what is funded;
- who holds authority;
- how work is prioritised;
- how value is measured; and
- how the portfolio can redirect investment.
If those mechanisms point in different directions, agility becomes local optimisation.
Decision Framework
Use a Strategic Agility Chain to test whether portfolio management can keep pace with delivery.
| Link | Executive test |
|---|---|
| Strategy | Can priorities change outside the annual planning cycle? |
| Funding | Can money move when evidence changes? |
| Capacity | Can scarce people move, or are they locked into existing commitments? |
| Governance | Are decision rights close enough to the information? |
| Metrics | Do measures show value and flow, not only baseline variance? |
| Delivery | Can teams adapt scope while preserving strategic intent and control? |
| Results | Are business outcomes compared with the evolving investment case? |
The portfolio is only as agile as its slowest critical link.
A team that can change in a week is constrained by a funding process that changes twice a year. A flexible funding model is constrained by scarce capability that cannot move. Decentralised product decisions are constrained if enterprise architecture requires lengthy central approval.
Strategic agility therefore requires system-level design.
Portfolio Reviews Must Change
A portfolio review for adaptive work should ask more than whether the initiative is on time.
It should examine:
- whether the strategic problem is still important;
- whether evidence is increasing or decreasing expected value;
- whether the value stream is consuming capacity proportionate to its importance;
- whether another initiative now has a stronger claim on funding;
- whether dependencies are preventing local adaptation;
- whether benefits are appearing in operations;
- whether the team has enough delegated authority to act on what it learns.
This does not weaken accountability. It changes accountability from adherence to an initial forecast toward disciplined use of evidence.
Related article: Portfolio Prioritisation Is Not Ranking: Decide What to Accelerate, Defer and Stop
From Strategy to Execution
Immediate action is to map the time required for a strategic change to reach delivery. Start with a realistic scenario: a customer shift, regulatory change or business-case deterioration. How long until priorities, funding, capacity and team backlogs actually change?
Medium-term capability is to align portfolio governance with mixed delivery models. Define how traditional projects, Agile teams and persistent value streams coexist. Update status definitions, funding rules and benefits tracking so different delivery methods can be compared without forcing them into inappropriate metrics.
Long-term positioning is to create resource mobility. Strategic agility is weak if every scarce specialist, supplier commitment and budget is fully allocated. Preserve some capacity for reprioritisation. Build modular architectures that reduce the cost of change. Develop leaders who can stop work as confidently as they start it.
Agility becomes strategic when the organisation can change commitments, not only plans.
Signals to Monitor
The organisation may be agile locally but rigid strategically when:
- sprint priorities change frequently while portfolio priorities rarely do;
- teams deliver more features but benefits do not improve;
- new priorities are announced without withdrawing old work;
- value streams exist in name but funding is still locked to projects;
- decentralised teams wait for central decisions on routine matters;
- portfolio reporting treats scope change as failure even when value increases;
- low-value work continues because annual budget ownership discourages reallocation;
- strategic reviews identify change but delivery commitments remain untouched.
Questions for the Leadership Team
- How long does it take us to move funding after a strategic priority changes?
- Which resources are too immobile for our stated level of agility?
- Are our portfolio measures compatible with the way teams actually deliver value?
- What decisions can product or value-stream leaders make without escalation?
- Which controls protect enterprise risk, and which simply preserve historical project habits?
- Can we stop a weak initiative as quickly as we can reprioritise a backlog?
- Where is the slowest link between strategic sensing and execution?
Closing Perspective
Agile delivery can increase organisational responsiveness, but it cannot create strategic agility by itself.
The enterprise becomes strategically agile when sensing, funding, capacity, governance and delivery move as a connected system. Faster teams expose slow portfolio mechanisms rather than compensate for them.
The executive task is therefore not to scale Agile ceremonies. It is to shorten the distance between evidence and enterprise commitment.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.