Chapter 1: Accelerate
Core Argument
Every industry depends on software to compete. Organizations must accelerate:
- Delivery of goods and services
- Engagement with the market to detect customer demand
- Anticipation of compliance and regulatory changes
- Response to security threats and economic changes
Software is the central differentiator. Banks no longer compete on gold vaults — they compete on trading speed, new channels, and customer engagement. Retailers win with superior online/offline experiences. Government delivers better public services through technology.
Why Most Efforts Fail: The Maturity Model Problem
Many organizations use maturity models to track DevOps progress. Forsgren et al. argue this is fundamentally wrong — maturity models should be replaced by capability models.
Maturity Models vs. Capability Models
| Maturity Models | Capability Models |
|---|---|
| Help you “arrive” at a mature state | Focus on continuous improvement |
| Linear/lock-step progression | Multidimensional and dynamic |
| Same path for all teams | Context-specific and customized |
| Measure technical proficiency as output | Outcome-based (tied to business impact) |
| Static level of achievement | Adapts to changing technology landscape |
| Vanity metrics | Meaningful metrics tied to outcomes |
The best companies are never “done” with improvement — they continually reach for gains.
What Doesn’t Predict Performance
Research found these factors do not predict delivery performance:
- Age and technology of the application (mainframe vs. greenfield)
- Whether ops or dev teams performed deployments
- Whether a Change Approval Board (CAB) is implemented
The 24 Capabilities
Research identified 24 key capabilities that drive software delivery performance in statistically significant ways. They fall into 5 categories:
- Continuous delivery
- Architecture
- Product and process
- Lean management and monitoring
- Cultural
The Performance Gap (2017 data)
High performers vs. low performers:
- 46x more frequent code deployments
- 440x faster lead time from commit to deploy
- 170x faster mean time to recover
- 5x lower change failure rate
The gap is widening over time — the best keep improving while laggards fall further behind.
Key Insight: Quality and Speed Are Not a Tradeoff
“High performers understand that they don’t have to trade speed for stability or vice versa, because by building quality in they get both.”
Low performers try to increase tempo without investing in quality → larger failures, more time to restore. This is the “work harder” anti-pattern.
Evidence-Based Transformation
The book provides something new: rigorous academic research methods applied to industry practice. Rather than relying on anecdote or the experience of a few teams, it uses cross-sectional studies (the same methods as healthcare research) to identify what actually drives performance.