There is a tidy fantasy at the center of most agile transformations. Adopt the framework, pass the assessment, collect the maturity certificate, and agility is achieved. It is a comforting model because it has an endpoint and a credential, and both are legible to the people funding the change. It is also wrong in a way that wastes a great deal of money. Agility is not a status you attain. It is a set of capabilities you build and keep building, and the moment you treat it as a certificate is the moment it starts to decay.
Performance traces to capabilities, not credentials
The most serious attempt to identify what actually drives software delivery performance did not find a certificate at the bottom of it. Forsgren, Humble and Kim (2018), in Accelerate, drew on four years of State of DevOps research and used statistical analysis to argue that specific organizational capabilities drive higher delivery performance. Their explicit target was the conventional wisdom that delivery-team performance does not matter for competitive advantage, and their answer was to name the capabilities that separate high performers from the rest. The unit of analysis is capability, something a team can do, not credential, something a team has been awarded.
That distinction is the whole argument. A capability is built through practice and can be lost through neglect. A certificate, once granted, sits on a wall regardless of what the team does next. When an organization optimizes for the certificate, it optimizes for the assessment day and not for the durable ability the assessment was supposed to indicate. The map becomes the territory, and the territory quietly degrades.
Capabilities live in context, which certificates ignore
The context research makes clear why a certificate is such a poor proxy. The DORA State of DevOps report (2024), surveying around 39,000 respondents, found that the same organizational realities that no certificate captures are decisive. Priority instability reduces productivity and drives burnout, persisting even under good leadership and documentation. Transformational leadership is associated with better performance. Internal developer platforms improve productivity but can trade against stability and throughput. These are living conditions of the organization, not boxes on a maturity checklist, and they move performance regardless of what any assessment recorded last quarter.
A maturity certificate is a snapshot. Capability is a moving picture. A team can pass every gate of a scaling assessment and still be sunk by priorities that will not hold still, a fact the DORA data (2024) makes plain and no certificate can override. The credential measures conformance to a model. Performance answers to context.
Principles are the capability that matters most
Underneath the technical capabilities sits a subtler one that certificates are especially bad at capturing: whether the principles have actually been internalized. Palopak and Huang (2024), surveying 298 practitioners, found that the perceived impact of the twelve Agile Manifesto principles, not the mechanical performance of practices, is what associates with project success. Internalized principle is a capability in the truest sense. It shows up in the thousands of small decisions a team makes when no assessor is watching, whether it genuinely welcomes a late requirement change or resents it, whether it really trusts motivated individuals or merely says so.
This is exactly what a certificate cannot see. An assessment can confirm that the ceremonies are present and the artifacts exist. It cannot confirm that the team believes in delivering value early or would defend that belief under deadline pressure. The scaling literature reinforces the point. Dikert, Paasivaara and Lassenius (2016), across 42 industrial cases, found success factors like mindset shift and customization, neither of which any credential confers. A mindset is not awarded. It is developed, and it can regress.
The practical read
Stop treating agility as a finish line with a certificate at the tape. The evidence describes a set of capabilities you build and maintain: the technical and organizational ones Forsgren, Humble and Kim (2018) traced to delivery performance, the contextual ones the DORA report (2024) shows are decisive, and the internalized principles Palopak and Huang (2024) found do the real work. None of them survive being treated as a one-time achievement. Dikert, Paasivaara and Lassenius (2016) even name mindset and customization as success factors, which are the two things a standardized certificate is structurally incapable of granting.
The organizations that get lasting value here are the ones that never believe they have arrived. They keep building the capabilities, keep stabilizing the context, and keep asking whether the principles are actually held or merely displayed. The certificate on the wall tells you what a team could do on assessment day. Only the capability tells you what it can do tomorrow, which is the only day that pays.
Sources
- Forsgren, Humble and Kim (2018). Accelerate: The Science of Lean Software and DevOps. Uses four years of State of DevOps data to argue that specific organizational capabilities, not credentials, drive delivery performance. https://itrevolution.com/product/accelerate/
- DORA / Google Cloud (2024). Accelerate State of DevOps Report 2024. Shows contextual factors such as priority stability and leadership move performance regardless of any maturity assessment, based on correlational survey data. https://dora.dev/research/2024/dora-report/
- Palopak and Huang (2024). Perceived impact of agile principles: Insights from a survey-based study on agile software development project success. Finds internalized adherence to the twelve Manifesto principles, not mechanical practice, associates with project success. https://doi.org/10.1016/j.infsof.2024.107552
- Dikert, Paasivaara and Lassenius (2016). Challenges and success factors for large-scale agile transformations: A systematic literature review. Identifies mindset shift and customization among success factors, neither of which a standardized certificate can confer. https://doi.org/10.1016/j.jss.2016.06.013