Large Agile transformations often stall after the visible mechanics are in place: teams exist, planning events happen, roles are assigned, and dashboards are full. Yet priority changes remain slow, dependencies remain painful, product ownership remains weak, and executive decisions still sit outside the delivery system.
That is not an Agile problem. It is an operating-model problem.
Agile methods can improve local delivery, but enterprise agility depends on portfolio choices, product structures, decision rights, architecture, funding, risk, leadership behavior, and the ability to resolve constraints that cross organizational boundaries.
What to preserve—and what to stop worshiping
Preserve
- Fast feedback
- Small batches
- Visible work
- Cross-functional collaboration
- Customer focus
- Continuous improvement
Do not confuse with outcomes
- Number of ceremonies
- Framework vocabulary
- Story-point volume
- Uniform team structures
- Training completions
- “Maturity” scores without business impact
A common failure pattern
The teams are Agile. The portfolio is not.
Teams plan in short cycles and expose work visibly, but priorities still arrive through annual planning, funding is locked to projects, dependencies require committee escalation, and executives insert urgent work without removing anything else. Local delivery becomes faster while the enterprise system keeps creating delay.
The tradeoff
Standardization can accelerate coordination—or suppress judgment.
Some common language, planning, and governance helps large organizations coordinate. Requiring identical team structures, ceremonies, and artifacts everywhere can turn a learning system into compliance. Standardize the interfaces and controls the enterprise truly needs; allow teams to adapt the practices inside them.
What enterprise agility actually requires
Fast strategic tradeoffs
Leaders can move capacity when evidence changes.
Meaningful product ownership
Accountability spans outcomes, not just backlog administration.
Flow across boundaries
Dependencies, approvals, architecture, risk, and operations are part of the system—not external obstacles.
Engineering capability
Automation, quality, DevSecOps, and continuous delivery support rapid learning.
Executive governance
Leadership forums reinforce prioritization, accountability, and correction.
Measures that matter
Customer, business, flow, reliability, quality, and risk signals replace activity theater.
Executive decision
Which constraints will leadership remove instead of asking teams to work around?
Choose the few enterprise constraints—portfolio overload, decision latency, architecture, risk queues, weak product ownership, cross-business dependencies—that most limit flow. If they stay untouched, another wave of training will not create enterprise agility.
Experience changes the answer
At enterprise scale, the correct approach is rarely “more framework.” At Edward Jones, the work included simplifying excessive framework complexity while preserving strategic alignment, product/value-stream accountability, governance, dependencies, feedback loops, and disciplined delivery. At Discover, the transformation connected Agile ways of working to operating-model design, DevSecOps, product/value-stream structures, governance, decision rights, and performance measures in an environment supporting more than 1,400 technology teams/pods.
The point is not to abandon Agile. It is to recover its economic purpose.