Executives who mandated stand-ups now face a harder truth: the rituals went in, the delays stayed, and burnout rose. Teams complete sprints, yet strategy pivots every quarter and backlogs are rewritten midweek. The latest DevOps survey of roughly 39,000 respondents links unstable organizational priorities with lower productivity and higher burnout, and that relationship holds even when leadership and documentation are rated strong (DORA, 2024). The problem is not the sprint. It is the churn.
What large-scale evidence actually says
A systematic review of 52 publications covering 42 industrial agile transformations found a thin evidence base. Nearly nine in ten papers were practitioner experience reports rather than academic studies, which should temper any claim of universal best practice (Dikert, Paasivaara and Lassenius, 2016). Even so, common patterns are clear enough to be useful. The review catalogued 35 distinct challenges and 29 success factors. The salient ones are not about ceremonies. They are about management support, customization of the model to context, training and coaching, and, above all, mindset and alignment across the organization (Dikert, Paasivaara and Lassenius, 2016).
This is the heart of the cargo-cult problem. Copying a visible routine without changing the conditions that make it work produces motion without progress. The review’s picture of success is not a textbook Scrum board. It is leadership that backs the change, teams coached to internalize new ways of working, and a model adapted to legacy constraints rather than imposed wholesale (Dikert, Paasivaara and Lassenius, 2016). Where those ingredients are missing, large-scale rollouts stall regardless of how many stand-ups are scheduled.
Productivity is a leadership variable more than a ceremony
The 2024 Accelerate State of DevOps Report offers a contemporary read on why many transformations feel busy yet brittle. In cross-sectional data, organizational priority instability is associated with substantial drops in productivity and higher burnout. That association persists even when respondents report strong leadership and solid documentation, suggesting that no amount of ritual or hygiene cancels out churn at the top (DORA, 2024). The same report finds that transformational leadership, defined as leaders who inspire, challenge, and support teams, correlates with better productivity, stronger organizational performance, and higher satisfaction, and it is linked with lower burnout (DORA, 2024). The evidence is correlational, not causal, but the pattern points in one direction. Leadership behavior and decision hygiene matter more than sprint mechanics.
Tools matter too, but only as part of a system. Internal developer platforms are associated with higher productivity at the individual, team, and organizational levels (DORA, 2024). That gain is easy to squander if priorities remain volatile, because speed without direction just burns fuel.
Capabilities, not theater
Before the current Google Cloud stewardship, the research program behind the DevOps reports argued for a sharper claim. Based on four years of data from the State of DevOps studies, Nicole Forsgren, Jez Humble, and Gene Kim contend that measurable team performance metrics and specific organizational capabilities drive higher software delivery performance. They position this as a direct challenge to the idea that delivery performance does not affect competitive advantage (Forsgren, Humble and Kim, 2018). Treat this as the authors’ claim rather than settled law, but take the managerial message seriously. If you cannot define, instrument, and improve the capabilities that move delivery, more rituals will not help.
This links back to the large-scale review. The capabilities need sponsorship, coaching, and customization to take root. Without senior support and alignment, teams are left to interpret frameworks as contracts rather than as operating systems to be tuned (Dikert, Paasivaara and Lassenius, 2016). Without stable priorities, even well-instrumented teams will see their measured performance sag as work is thrashed through the system (DORA, 2024). Agile becomes a theater of participation that hides a portfolio process still run by fiat.
What to change on Monday
If the bottleneck is context, not cadence, start where context is set.
-
Stabilize priorities. Establish clear decision rights for what can change mid-sprint, and publish a predictable cadence for portfolio updates. The 2024 DevOps data show that unstable priorities co-move with lower productivity and more burnout, even in settings with strong leaders and documentation (DORA, 2024). The practical countermeasure is to reduce churn at the source.
-
Put leadership on the hook. Treat management support as a deliverable, not a sentiment. Name an executive sponsor who shields teams from priority whiplash and funds coaching. The systematic review lists management support and coaching among the most cited success factors for large-scale transformations (Dikert, Paasivaara and Lassenius, 2016).
-
Customize the model. Resist template rollouts. Adapt the approach to your architecture, compliance posture, and customer cadence. The review repeatedly flags customization, alignment, and mindset as necessary for success across diverse industrial contexts (Dikert, Paasivaara and Lassenius, 2016).
-
Invest in platform enablement, not tool sprawl. Create common services that remove toil and speed safe changes. The 2024 report associates internal developer platforms with higher productivity at multiple levels. Pair that with clear ownership and guardrails so the platform accelerates delivery rather than centralizing decisions (DORA, 2024).
-
Measure to learn, not to police. Use a small, visible set of delivery performance metrics, and review them to improve the system rather than to rank individuals. The authors of Accelerate argue that measurable team performance and the organizational capabilities that support it are foundational to better outcomes and strategic advantage (Forsgren, Humble and Kim, 2018).
The practical implication is blunt. If you have budget for one change, spend it upstream. Stabilize priorities and make executives own the conditions for flow. The ceremonies can help, but only when they sit on top of leadership that commits, context that stays steady long enough for teams to finish, and capabilities that compound over time. Agile beyond the ritual is not softer Scrum. It is management by design rather than by meeting.
Sources
- Dikert, Paasivaara and Lassenius (2016). Challenges and success factors for large-scale agile transformations (Systematic Literature Review). Finds 35 challenges and 29 success factors across 42 industrial cases, with management support, customization, coaching, and alignment as salient drivers, supporting the argument that context outweighs ritual. https://www.sciencedirect.com/science/article/pii/S0164121216300826
- DORA / Google Cloud (2024). Accelerate State of DevOps Report 2024. In cross-sectional survey data of roughly 39,000 respondents, unstable priorities co-occur with lower productivity and higher burnout, while transformational leadership and internal developer platforms are associated with better outcomes, underscoring leadership and context over ceremony. https://dora.dev/research/2024/dora-report/
- Forsgren, Humble and Kim (2018). Accelerate: The Science of Lean Software and DevOps. Argues, based on four years of State of DevOps data, that measurable team performance and specific organizational capabilities drive higher delivery performance and matter for competitive advantage, reinforcing a capabilities-over-ritual stance. https://itrevolution.com/product/accelerate/