Introduction
For more than a decade, the Agile vs. Waterfall debate has shaped how organisations think about project delivery. Agile has been positioned as the modern, nimble alternative to the rigid, outdated structures of traditional project management. When executive teams are asked the question ‘would you like to be more agile, more efficient and more productive?’ there is only one answer. A resounding ‘Yes!’. From a consulting or training perspective, the Agile vision is an easy one to sell. However, the implementation is rarely as straightforward as the pitch. Often, in the rush to ‘go Agile,’ organisations make sweeping structural and procedural changes, removing layers of governance, disbanding PMOs, and encouraging delivery teams to operate autonomously.
In theory, this unlocks speed and innovation. In practice, if due care isn’t taken, it often results in a lack of visibility, inconsistent delivery outcomes and strategic misalignment. Senior leaders, once able to track progress across portfolios, now find themselves asking some basic questions: What are we delivering? How do we know it’s working? Where is the risk? And critically, how do we know we’ve realised the value?
While delivery teams accelerate their pace, executive leaders often lose visibility, lack assurance, and struggle to see what’s being delivered, how risks are managed, or whether strategic outcomes are being achieved.
When done right, Agile transformations drive greater efficiency and productivity, but without the right foundations, they leave organisations in the dark, unclear about what’s actually being delivered. The real challenge isn’t adopting agile practices; it’s designing a delivery ecosystem where the right levels of autonomy and accountability can coexist.
This article seeks to explore what happens in the aftermath of an Agile transformation. Drawing on real world experiences, we look at how organisations are moving beyond the buzzwords and sharing lessons from post-Agile transformation and aiming to support organisations to reintroduce the right level of control, without compromising the principles of agility.
The Agile Dream – And Where It Can Go Wrong
In 2001, a group of software practitioners gathered to develop what would become the Agile Manifesto, a set of guiding principles aimed at transforming how software was developed. These principles focused on collaboration, responsiveness, and working solutions over rigid processes. Principles which can and should be applied across many business landscapes. Over time, Agile principles became codified, commercialised, and, in many cases, misinterpreted. Often being lauded as a new project management approach and splintering into many different types of methodology, many with associated training courses, certifications and a whole ecosystem of systems and tools. Agile was no longer a mindset; it became a product.
Many organisations adopt Agile as a one-size-fits-all project management methodology. Vendors and internal champions often sell it as a panacea for delivery challenges, and teams implement it without fully understanding what they’re gaining, or what they’re giving up. In the rush to ‘be Agile,’ they frequently sacrifice governance, structure, and strategic alignment, with little regard for the long-term consequences.
The result? Agile has become less about delivering value and more about following rituals, adopting jargon, and ticking boxes. Often at the expense of clarity, accountability, and optimum delivery outcomes.
Governance Isn’t the Enemy
In some agile transformations, governance has become the scapegoat for everything slow, bureaucratic, or misaligned with delivery. But in truth, governance isn’t the enemy of agility, it’s one of its critical enablers.
Good governance creates clarity, not constraint. It defines the operating environment within which delivery teams can move fast, take calculated risks, and escalate issues when necessary. It’s not about imposing unnecessary process, it’s about ensuring there’s enough structure to maintain momentum without compromising accountability.
At its best, governance provides:
- Visibility into delivery across portfolios, so that leadership knows what’s happening, where, and why.
- Decision rights and escalation paths, so that issues don’t stagnate and delivery teams aren’t left to navigate ambiguity alone.
- Risk-aligned assurance layers, so that oversight is proportionate to complexity, cost, and criticality.
The fallacy that ‘Agile means no governance’ is both dangerous and false. Even in scaled frameworks like SAFe, LeSS, and Disciplined Agile, governance is (or should be) embedded, just implemented differently. Scaled Agile Frameworks are amongst the most likely transformations to be poorly executed, (https://www.engprax.com/post/268-higher-failure-rates-for-agile-software-projects-study-finds/) due to their complexity, the level of cultural change required, and the mistaken belief that adopting a framework equates to achieving agility.
In many cases, organisations attempt to implement frameworks like SAFe or LeSS as a checklist exercise, rolling out ceremonies, artefacts, and new job titles without addressing the underlying mindset shift or operating model alignment. The result is often a thin layer of agile terminology plastered over a fundamentally unchanged structure. Or worse, a stripped back structure devoid of decision rights, delivery accountability, or strategic alignment, leaving teams overwhelmed, leadership disengaged, and the business exposed to a sharp increase in delivery risk.
This kind of transformation doesn’t enable agility, it undermines it. Agile becomes a label, not a capability.
Without deliberate change management, clear leadership commitment, and a strong understanding of why these frameworks exist, not just what they prescribe, scaled transformations often become bloated, performative, ineffective and expensive.
Cadence-based planning, lightweight approval processes, embedded product ownership, and real-time dashboards are all important forms of governance. They just don’t look like a traditional steering committee. Each organisation must decide and deliver what the minimum viable governance measures are, to provide the leadership team with the confidence it needs to maintain strategic decision making.
We recently worked with a client who had removed almost every formal decision-making forum in the name of agility. Teams were working quickly, but in silos. When key decisions needed cross-functional input, there was nowhere to go. Teams felt unsupported, and leadership couldn’t intervene constructively. The result was confusion, delay, and delivery risk. Agile delivery still needs guardrails and transparency.
Post-Agile Realities – What Organisations Are Now Asking
Years after agile transformations were first rolled out, many organisations are still grappling with structural gaps that were never fully addressed. The vision was autonomy and speed; the reality, in many cases, is ambiguity, fragmentation, and a lack of strategic oversight.
These are the questions we’re hearing more and more:
- “How do we reintroduce just enough control—without reverting to bureaucracy?”
- “Can we gain meaningful portfolio visibility without going back to waterfall reporting?”
- “Where’s the line between agility and risk exposure—and how do we manage it?”
These questions mark a shift. It’s no longer about being agile at all costs—it’s about being in control while staying responsive. Agile has moved from concept to consequence, and leadership is grappling with what’s missing.
The common pain points we’re seeing include:
- A lack of reliable delivery forecasting—teams are working, but outcomes remain unpredictable
- No clarity on benefit realisation, initiatives are completed, but with no clear evidence of impact
- No clear escalation paths or strategic adjustment mechanisms, issues bubble without resolution, while misaligned work continues
What all of this signals is a broader evolution, a shift from hype to maturity. Leaders aren’t questioning agile itself; they’re questioning how it’s being applied. What they want now is agility with accountability, a delivery environment where autonomy is matched by insight, and responsiveness is backed by rigour.
Finding the Balance—Designing Fit-for-Purpose Delivery Models
It’s time to reject the binary thinking that has plagued delivery model discussions for years. It’s not simply a choice between Agile or Waterfall, it’s about designing a model that fits your organisation’s risk appetite, delivery context, and project profile.
At Pledge, we work with clients to co-create delivery frameworks that are both adaptive and accountable. Our approach focuses on:
- Co-designing frameworks aligned to business outcomes, not just delivery preferences
- Layering governance in a way that supports delivery teams, rather than stifling them
- Using cadences that reflect complexity, because not every initiative needs a two-week sprint
We advocate for a layered governance model, where oversight is proportionate to the stakes involved:
- A low-risk innovation pilot might only need light-touch reporting and oversight from a single sponsor
- A cross-agency infrastructure program, by contrast, may warrant formal checkpoints and staged delivery assurance
Hybrid models aren’t a compromise, they’re often the most mature response. Blending agile ceremonies with traditional disciplines, like gated funding approvals, decision points, and formal benefits reviews can work seamlessly if the model is intentionally designed.
There are also practical tools that support this balance:
- Lightweight portfolio dashboards that provide visibility without the reporting burden
- Decision trees that allocate governance based on initiative tier, risk, or value
- Embedded assurance roles that work alongside delivery teams—not as external auditors, but as trusted enablers of quality and alignment
The outcome is a delivery model that’s not only fast, it’s fit-for-purpose, sustainable, and aligned to strategy.
While there’s no shortage of consultants and frameworks promising agility ‘out of the box,’ agility isn’t a product, it’s a capability that needs to be built in context. Off-the-shelf solutions can be helpful starting points, but when applied without regard for culture, leadership maturity, or delivery constraints, they often create more noise than value. The most effective transformations aren’t sold, they’re co-designed, evolved, and embedded over time. Any delivery model worth implementing should feel like it fits, not like it’s been forced in.
Leadership’s Role in the New Agile
In a post-transformation environment, the role of leadership becomes even more critical through creating the conditions where delivery thrives.
Leaders need to focus on clarity, confidence, and culture. That means:
- Defining outcomes, priorities, and non-negotiables—so teams understand where they’re heading and what really matters
- Fostering psychological safety—but not at the expense of accountability. Teams need space to experiment and the discipline to follow through
- Enabling delivery teams, not managing them. Leaders should remove obstacles, provide direction, and trust people to do the work
But above all, leadership must be brave enough to challenge the orthodoxy. That means pushing back on frameworks, methodologies, and even external experts when what’s being sold doesn’t fit the organisation’s needs. The goal shouldn’t be to implement Agile, it’s to deliver value. That takes discernment, not dogma.
A recurring issue we see is the loss of strategic alignment. Agile teams often become operationally effective but strategically disconnected. Without a clear link back to enterprise objectives, delivery can become fragmented, duplicative, or misaligned with where the organisation is heading.
This is where leadership must stay connected and visible, not necessarily in the day-to-day, or on the ground sense, but in consistently reinforcing the why. Connecting delivery decisions to strategic intent is the pathway to true transformation success.
PMOs can also have a key role to play in making this happen. A high-performing PMO doesn’t just govern—it enables:
- By reframing its role from compliance checker to strategic enabler
- By championing tools that provide fit for purpose transparency and timely insights
- And by acting as a translator between delivery teams and executive leadership, ensuring both sides operate with the same information and intent
When this partnership is in place, governance becomes less about control and more about cohesion and coordination.
Practical Lessons from the Field
Too often, frameworks are adopted wholesale without interrogation. But effective leaders understand that agility isn’t a compliance exercise, it’s often a judgement call. It takes courage to question the default advice, to challenge so-called best practice, and to push back on rigid interpretations of frameworks or methodologies when they’re not serving the organisation’s best interest. Leaders must be willing to say, ‘This might be the standard, but is it right for us?’ That means taking a clear-eyed view of what the business actually needs, rather than what’s fashionable or what a consultant recommends, and making deliberate, contextual decisions that serve outcomes over orthodoxy. Agility doesn’t come from blind adoption. It comes from critical thinking, customisation, and the confidence to lead with what works.
Conclusion
Agile transformations are not the final destination, they’re just the beginning. What comes next is the harder work: embedding practices, aligning intent with execution, and building the kind of delivery maturity that actually moves the business forward.
Agile shouldn’t mean chaos. Waterfall shouldn’t mean bureaucracy. The best delivery models aren’t binary, they’re contextual. They reflect the complexity, risk, and culture of the organisation they serve.
Success isn’t about following a framework. It’s about understanding what your business needs, what your people are capable of, and how your strategic priorities can be delivered with clarity, pace, and confidence.
The organisations thriving post-transformation are those willing to rethink the rules without abandoning the purpose behind them. Balancing innovation with discipline, and autonomy with accountability.
Want to explore what fit-for-purpose delivery could look like in your organisation?
Let’s have a conversation. Whether you’re recovering from an agile transformation, building a hybrid model, or simply looking to improve delivery outcomes, we can help you design a governance and delivery framework that actually works. Talk to us today!
