Executives are mandating agile while priorities lurch from quarter to quarter. Teams keep the ceremonies, yet outcomes stall and burnout rises. The pattern is familiar: a framework is rolled out, sticky notes bloom, and nothing essential changes about how decisions, priorities, and platforms work. The problem is not the ritual. It is the system that surrounds it.
The ritual trap
The most comprehensive look at large-scale agile transformations found something awkward for anyone selling a one-size-fits-all framework. In a systematic literature review covering 52 publications and 42 industrial cases, almost 90 percent of the included papers were practitioner reports rather than academic studies, a sign that the evidence base for scaling agile is thin and highly contextual (Dikert, Paasivaara and Lassenius, 2016). The review catalogued 35 distinct challenges and 29 success factors. The items that recur are not sprint mechanics. They are management support, tailoring the model to the organization, training and coaching, mindset, and alignment across units (Dikert, Paasivaara and Lassenius, 2016). In other words, the failure mode is cultural and structural, not procedural. Cargo-cult agile is not a meme. It is a diagnosis.
This aligns with the 2020s reality of hybrid teams, shifting strategies, and platforms in flux. When leaders oscillate on priorities or run transformations as tool deployments, ceremonies cannot rescue outcomes. The review’s core implication is plain: treat agile as an organizational change with executive sponsorship and adaptation to context, or expect reversion to old habits behind new labels (Dikert, Paasivaara and Lassenius, 2016).
What the data says about friction
If you want a quantified picture of what really drags delivery, look at the latest large-scale survey data. The 2024 Accelerate State of DevOps report, based on roughly 39,000 respondents, associates instability of organizational priorities with lower productivity and higher burnout, and this negative association persists even when leadership quality and documentation are rated as good (DORA/Google Cloud, 2024). That finding challenges a common rescue plan in stalled agile adoptions: train the managers, improve the docs, and expect the rest to follow. The survey suggests that if strategy churns, people burn out and throughput falls regardless.
The same dataset links transformational leadership, leaders who inspire, stimulate intellectually, and support teams, with higher productivity, stronger organizational performance, greater satisfaction, and lower burnout (DORA/Google Cloud, 2024). The correlation does not prove causation, and the report itself is cross-sectional, but it draws a useful boundary. Agile without leadership that sets direction, removes obstacles, and nurtures autonomy tends to degrade into ceremony chasing. Conversely, leadership quality is associated with the very outcomes agile is meant to advance.
Platform choices also matter. Internal developer platforms are associated with improvements in individual, team, and organizational productivity, but they can come with trade-offs in stability and change throughput that leaders should monitor and manage deliberately (DORA/Google Cloud, 2024). Again, these are associations, not experimental results. The practical read is that adding a platform is not a substitute for clarifying priorities or strengthening leadership. It is a lever with benefits and potential costs that must be measured.
Capabilities over ceremonies
The most influential synthesis of the past decade argues that what separates high performers from the rest are specific, measurable capabilities, not adherence to a particular ritual set. Drawing on several years of State of DevOps data, Forsgren, Humble and Kim argue that a small number of software delivery performance metrics and organizational capabilities causally drive better outcomes, and they position this against the once-common claim that delivery team performance does not materially affect competitiveness (Forsgren, Humble and Kim, 2018). Their book won a Shingo Institute Publication Award, which speaks to its influence in operations circles (Forsgren, Humble and Kim, 2018). While the book’s causal language reflects the authors’ analysis and should be read as their claim, the direction is clear. Focus on capabilities that create fast feedback, reliable flow, and a culture of continuous improvement, not on rote compliance with a framework.
Taken together, the literature review and the survey results point to the same conclusion. Agile rituals help only when embedded in an operating system that stabilizes priorities, aligns incentives, invests in enabling platforms with eyes open to trade-offs, and develops leaders who serve the teams doing the work. Without that, you get velocity theater.
How to run agile beyond ritual
Start with the one variable teams cannot fix themselves: strategic stability. Set fewer priorities and keep them stable over the planning horizon. The 2024 survey associates instability with productivity loss and burnout that leadership quality and documentation do not offset, so treat stability as a first-class constraint in portfolio governance (DORA/Google Cloud, 2024).
Treat executive sponsorship as a behavior, not a slogan. The systematic review flags management support and alignment as recurrent success factors, which means senior leaders must remove cross-team blockers, reconcile conflicting goals, and reinforce trade-offs in public, repeatedly (Dikert, Paasivaara and Lassenius, 2016).
Customize the framework to fit how your business makes money. The review emphasizes tailoring over templating, supported by coaching and training, and a mindset shift that respects local context (Dikert, Paasivaara and Lassenius, 2016). Pick a small number of delivery and reliability metrics, make them visible, and iterate the operating model as you learn. This stance reflects the capabilities-first approach that Forsgren, Humble and Kim argue drives performance gains (Forsgren, Humble and Kim, 2018).
Invest in platform enablement with measurement in hand. If you adopt an internal developer platform, track both the productivity gains and any changes in stability and throughput, since the 2024 survey flags potential trade-offs alongside the benefits (DORA/Google Cloud, 2024). Manage the platform as a product with clear ownership, service levels, and user feedback, rather than as a tooling rollout.
Finally, select and develop leaders for transformational behaviors. The 2024 data links these behaviors with better outcomes and lower burnout, which is consistent with the review’s emphasis on mindset and support as success factors, not just process compliance (Dikert, Paasivaara and Lassenius, 2016; DORA/Google Cloud, 2024). Do not subcontract leadership development to the framework. Make it a core workstream of the transformation.
Agile is not a ceremony kit. It is a bet that small teams, aligned to clear goals, in a system designed for flow and learning, will outpace bureaucracy. The evidence base is patchy and much of it is experience-based, which argues for humility and measurement, not dogma (Dikert, Paasivaara and Lassenius, 2016). If you stabilize priorities, back teams with real leadership, and build capabilities rather than police rituals, you give that bet a fair chance to pay off.
Sources
- Dikert, Paasivaara and Lassenius (2016). Challenges and success factors for large-scale agile transformations, Journal of Systems and Software. A systematic review of 52 publications finds a weak, experience-heavy evidence base and highlights management support, tailoring, coaching, mindset, and alignment as central success factors. https://www.sciencedirect.com/science/article/pii/S0164121216300826
- DORA/Google Cloud (2024). Accelerate State of DevOps Report 2024. A large cross-sectional survey associates unstable priorities with lower productivity and higher burnout, links transformational leadership with better outcomes, and notes platform benefits with possible trade-offs. https://dora.dev/research/2024/dora-report/
- Forsgren, Humble and Kim (2018). Accelerate: The Science of Lean Software and DevOps. Argues that specific capabilities and metrics drive better delivery performance and positions delivery as a source of competitive advantage; widely influential in operations. https://itrevolution.com/product/accelerate/