Executives reissuing return‑to‑office memos and rebooting agile transformations share a reflex: add more standups and tighter cadences to recover speed. The data points in the opposite direction. When priorities churn, productivity drops and burnout rises, and that penalty persists even when leadership quality and documentation are strong (DORA, 2024). No ceremony can offset a strategic zigzag.
What survives large-scale transformations
The most comprehensive look at large-scale agile changes is sobering. A systematic review of 52 publications covering 42 industrial cases found that nearly 90 percent of the evidence base consists of practitioner reports rather than academic studies, so claims about what works at scale rest on uneven ground (Dikert, Paasivaara and Lassenius, 2016). Even with that caveat, the pattern is consistent. The review identified 35 distinct challenges and 29 success factors. The factors that recur are not ritualistic. They center on visible management support, tailoring the model to the organization, sustained training and coaching, and a shift in mindset and alignment, not box‑ticking on Scrum events (Dikert, Paasivaara and Lassenius, 2016).
That matters in 2026 because many firms treat agile as choreography. They add standups to teams overloaded with conflicting initiatives, then declare the method broken when outcomes stall. The review suggests a different diagnosis. Without leadership air cover, clear alignment, and context-specific adaptation, the ceremonies create motion without change (Dikert, Paasivaara and Lassenius, 2016).
Fix the system before the ceremony
Fresh survey data reinforces the point with a wider lens. The 2024 State of DevOps Report associates unstable organizational priorities with sharply lower productivity and higher burnout, and notes that this effect remains even where leadership is rated highly and documentation practices are strong (DORA, 2024). The study is cross‑sectional and correlational, so it does not prove causation, but the pattern is consistent with what teams experience when roadmaps swing and reorgs cascade. Agile rituals cannot create flow in a system that keeps changing the destination.
The same report links transformational leadership with better productivity, stronger organizational performance, and higher satisfaction, alongside lower burnout (DORA, 2024). Again, correlations are not causation, yet they align with the success factors in the large-scale review where leadership support and mindset shifts are prominent (Dikert, Paasivaara and Lassenius, 2016). If you have to choose between another ceremony and a manager who coaches, protects focus, and stimulates better problem solving, choose the manager.
Tooling choices show similar trade-offs. Internal developer platforms are reported to improve productivity at the individual, team, and organizational level, yet they may correlate with reduced stability and throughput of change if implemented poorly (DORA, 2024). That is a reminder to treat platforms as products with clear outcomes and guardrails, not as silver bullets. The mechanism is practical: platforms that remove toil and clarify paths speed work; platforms that add complexity or generate dependency queues slow it. The study cannot assign causality, but it flags a risk leaders should manage (DORA, 2024).
Capabilities beat choreography
There is a deeper thesis behind these observations. Over four years of research that underpinned early State of DevOps studies, Forsgren, Humble and Kim argue that measurable software delivery performance matters for competitive advantage, and that specific organizational capabilities drive it (Forsgren, Humble and Kim, 2018). The authors position this against the old belief that delivery teams do not move the business needle. The book claims to identify the performance metrics and the capabilities that causally improve them, and it was recognized with the Shingo Institute Publication Award (Forsgren, Humble and Kim, 2018). While the field has debated methods and causality, the thrust is clear. Invest in capabilities that let teams deliver and learn quickly, and the business benefits follow.
Read together, these sources trace a line. Rituals are scaffolding. The load-bearing elements are leadership that protects focus and encourages improvement, a system with stable priorities, and deliberate investment in delivery capabilities. Absent those, agile becomes theater.
A short playbook for leaders
These moves are practical interpretations of the evidence and should be tailored to context:
- Stabilize the strategic lane. If the roadmap swings weekly, standups will only amplify noise. Reduce priority churn and make trade-offs explicit. This aligns with the DORA finding that unstable priorities correlate with lower productivity and higher burnout, with no observed mitigators in leadership or documentation ratings (DORA, 2024).
- Make leadership the first capability. Develop managers to set clear goals, coach, and advocate for teams. The 2024 report links transformational leadership with higher productivity and satisfaction and lower burnout, a pattern that rhymes with the success factors in large-scale transformations where management support and mindset are pivotal (DORA, 2024; Dikert, Paasivaara and Lassenius, 2016).
- Tailor the operating model, then train. Copy‑pasting a framework is cheaper than coaching, but the review highlights customization and sustained training as recurrent success factors (Dikert, Paasivaara and Lassenius, 2016). Start from constraints and value streams, not from a template.
- Invest in delivery capabilities, measure outcomes. Treat flow, quality, and reliability as management concerns, not team hobbies. This reflects the argument that organizational capabilities and measurable delivery performance matter for competitive advantage (Forsgren, Humble and Kim, 2018).
- Treat platforms as products. If you adopt an internal developer platform, define the outcomes and manage the trade-offs, since reported correlations include both productivity gains and risks to stability and change throughput (DORA, 2024).
The present tension will not fade. Boards want speed and resilience, and frontline teams are tired. The shortest path runs through management choices that stabilize priorities, sponsor real capability building, and adapt practices to context. Ship outcomes, not rituals.
Sources
- Dikert, Paasivaara and Lassenius (2016). Challenges and success factors for large-scale agile transformations: A systematic literature review, Journal of Systems and Software. Reviews 52 publications across 42 cases, finding a weak evidence base and highlighting management support, customization, training, and mindset/alignment as recurrent success factors. https://www.sciencedirect.com/science/article/pii/S0164121216300826
- DORA (2024). Accelerate State of DevOps Report 2024. Reports that unstable organizational priorities correlate with lower productivity and higher burnout even with strong leadership and documentation, that transformational leadership correlates with better outcomes, and that internal platforms correlate with productivity gains but potential stability trade-offs. 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 research behind the State of DevOps, that organizational capabilities and measurable delivery metrics drive performance and competitive advantage. https://itrevolution.com/product/accelerate/