Return-to-office fights, AI deadlines, and rolling cost cuts have pushed many firms back into ritual. Stand-ups get longer, backlogs swell, and leadership insists it is “doing agile.” Then the work stalls. The problem is not the daily ceremony. It is the system upstream of it: executive churn on priorities, weak sponsorship, cargo-cult rollouts, and a refusal to tailor the model to how the business actually makes money.
The real blocker sits above the team
If priorities keep changing, agile will not save you. In a global survey of roughly 39,000 respondents, DORA reports that unstable organizational priorities are associated with lower productivity and higher burnout, and that this penalty persists even when leadership quality and documentation are strong (DORA, 2024). That finding is correlational, not causal, yet the implication for practice is clear. When strategy whipsaws, no stand-up or sprint cadence can create focus. Teams execute in jerks, leaders spend political capital reprioritizing the reprioritization, and everyone gets tired.
This is why so many “transformations” look convincing on paper and thin in results. Teams rebrand their meetings, a new tool appears, and a big room planning photo circulates. The upstream system remains untouched. DORA also finds that transformational leadership, the kind that inspires, stretches people intellectually, and supports teams, is associated with better productivity, stronger organizational performance, higher satisfaction, and lower burnout (DORA, 2024). Again, the data are cross-sectional. Even so, the pattern lines up with what seasoned operators know: if leaders do not set and hold coherent priorities, sponsor the change, and remove obstacles, the mechanics of agile cannot carry the load.
Rituals without power do not change how work flows
Look at the best field synthesis we have on scaling agile in industry. Dikert, Paasivaara and Lassenius reviewed 52 publications covering 42 large-scale agile cases and found that almost 90 percent were practitioner reports rather than academic studies, a reminder that the evidence base here is thin and should be read for insight, not proof (Dikert, Paasivaara and Lassenius, 2016). Even so, the signal is consistent. The review identifies dozens of challenges and success factors. The standouts are managerial support, tailoring the method to context, training and coaching, mindset, and alignment across the organization (Dikert, Paasivaara and Lassenius, 2016). In other words, the failures look cultural and structural, not procedural.
That matches what many see on the ground. A framework that is copied verbatim from a slide deck tends to produce a performance of agility rather than the thing itself. Teams go through the motions while dependencies, incentives, and decision rights stay frozen. The literature’s emphasis on customization is a corrective. Agile is a means to manage uncertainty and learning. It must be fitted to your product cycle, regulatory risk, and customer promise. A bank’s change window is not a game studio’s release rhythm. The review’s finding on coaching also matters. You cannot “announce” a new way of working into existence. People learn it in practice, with help.
Measure capabilities, not ceremonies
If the rituals are not the lever, what is? Forsgren, Humble and Kim argue that a small set of measurable delivery performance metrics and specific organizational capabilities drive better software delivery outcomes, based on several years of State of DevOps research analyzed with statistical methods (Forsgren, Humble and Kim, 2018). The book positions itself against the claim that delivery team performance is irrelevant to competitive advantage and presents a model for improving it. These are the authors’ claims, not experimental proof, yet the direction chimes with the broader pattern. Focus on capabilities that let teams ship safely and often, and on removing the systemic friction that makes shipping hard.
That system includes leadership and platforms. DORA reports that transformational leadership is linked with better outcomes, and that internal developer platforms are associated with higher productivity at the individual, team, and organizational level (DORA, 2024). Read that as a prompt to invest in the enabling environment. If onboarding a service takes days, or if developers spend half their week waiting for environments, no amount of backlog grooming will reclaim the time. Conversely, when paved paths, automation, and clear guardrails exist, teams can spend their attention on customer value instead of wrestling the plumbing.
The harder truth here is about trade-offs. Governance exists for a reason. Many firms need traceability, segregation of duties, and risk controls. Agile beyond the ritual is not a license to ignore them. It is a discipline of making the work visible, choosing limits that support learning, and changing the process when evidence shows it hinders delivery. That is why tailoring shows up as a success factor. Copying a template is fast. Fitting a method to a business takes judgment and time.
How to run the next quarter differently
Treat the next 90 days as an audit of priorities, sponsorship, and capability, not as another process rollout.
- Stabilize intent. Publish a short, ranked list of outcomes that will not change for one or two increments. When something new arrives, state explicitly what drops. This directly addresses the priority churn that DORA associates with lower productivity and higher burnout (DORA, 2024).
- Put senior sponsors on the hook. Name the executive who will remove cross-team impediments each week. The SLR’s emphasis on management support is a warning. Without it, transformations tend to stall in middle management (Dikert, Paasivaara and Lassenius, 2016).
- Fund coaching, not posters. Budget for hands-on coaching at team and program levels. The literature lists training and coaching as frequent success factors because people change how they work through guided practice, not memos (Dikert, Paasivaara and Lassenius, 2016).
- Tailor on purpose. Start with the minimum set of practices that help your context, then adapt in the open. Write down why a practice exists, what problem it solves, and what evidence would justify changing it. The SLR highlights customization as a recurring ingredient in success (Dikert, Paasivaara and Lassenius, 2016).
- Measure capabilities that matter. Use a small set of delivery performance measures to see whether your changes are helping. The argument in Accelerate is to focus on measurable capabilities that link to delivery performance, not on ceremony compliance (Forsgren, Humble and Kim, 2018).
- Invest in the platform. Identify the two or three developer experience bottlenecks that burn the most hours, then fix them. DORA reports that internal developer platforms correlate with higher productivity, which is consistent with the idea that enabling infrastructure multiplies human effort (DORA, 2024).
None of this requires you to abandon agile. It asks you to stop treating it as theater. If leadership holds priorities steady, sponsors the change, and funds the capabilities that make delivery smoother, the rituals regain their purpose. The alternative is well known: more meetings that create the appearance of control while the work itself gets slower. The better path is to make agility the consequence of clarity and support, not a script for teams to recite.
Sources
- Dikert, Paasivaara and Lassenius (2016). Challenges and success factors for large-scale agile transformations. A systematic review of 52 publications across 42 cases finds the evidence base is mostly practitioner reports and highlights management support, customization, coaching, mindset, and alignment as frequent success factors, underscoring that culture and sponsorship matter more than ritual. https://www.sciencedirect.com/science/article/pii/S0164121216300826
- DORA (2024). Accelerate State of DevOps Report 2024. A large cross-sectional survey links unstable organizational priorities to lower productivity and higher burnout and associates transformational leadership and internal developer platforms with better outcomes, reinforcing that context and leadership shape results more than ceremonies. https://dora.dev/research/2024/dora-report/
- Forsgren, Humble and Kim (2018). Accelerate: The Science of Lean Software and DevOps. Drawing on several years of State of DevOps research, the authors argue that a small set of measurable delivery performance metrics and organizational capabilities drive better outcomes, supporting a shift from ritual compliance to capability building. https://itrevolution.com/product/accelerate/