Accelerate: Building and Scaling High Performing Technology Organizations
Authors: Nicole Forsgren, Jez Humble, Gene Kim
Published: 2018
Research basis: 4-year State of DevOps Report program (2014–2017), 23,000+ survey responses, 2,000+ organizations
Core Thesis
Software delivery performance is measurable, improvable, and directly predicts organizational performance (profitability, productivity, market share). High performers don’t trade speed for stability — they achieve both simultaneously by improving the right capabilities.
The Four Key Metrics (DORA Metrics)
| Metric | What it measures |
|---|---|
| Deployment Frequency | How often code is deployed to production |
| Lead Time for Changes | Time from code commit to running in production |
| Mean Time to Restore (MTTR) | How long to restore service after an incident |
| Change Failure Rate | % of changes that cause degraded service |
2017 Performance Benchmarks
| High | Medium | Low | |
|---|---|---|---|
| Deploy Frequency | On-demand (multiple/day) | 1/week–1/month | 1/week–1/month* |
| Lead Time | < 1 hour | 1 week–1 month | 1 week–1 month* |
| MTTR | < 1 hour | < 1 day | 1 day–1 week |
| Change Fail Rate | 0–15% | 0–15% | 31–45% |
Key finding: In 2017, high performers had 46x more frequent deploys, 440x faster lead time, 170x faster MTTR, and 5x lower change failure rate than low performers.
The 24 Capabilities (grouped)
Continuous Delivery (8)
- Version control for all production artifacts
- Deployment automation
- Continuous integration
- Trunk-based development
- Test automation
- Test data management
- Shift left on security
- Continuous delivery (CD)
Architecture (2)
- Loosely coupled architecture
- Empowered teams (tool choice)
Product & Process (4)
- Customer feedback
- Value stream visibility
- Small batch work
- Team experimentation
Lean Management & Monitoring (5)
- Lightweight change approval (peer review, not CAB)
- Monitoring to inform business decisions
- Proactive system health checks
- WIP limits
- Visual work displays
Cultural (5)
- Generative culture (Westrum)
- Learning culture
- Cross-team collaboration
- Meaningful work & tools
- Transformational leadership
Key Causal Chain
Transformational Leadership
↓
Technical Practices + Lean Management + Lean Product Management
↓
Continuous Delivery + Generative Culture
↓
Software Delivery Performance
↓
Organizational Performance + Employee Well-being
Book Structure
| Part | Chapters | Focus |
|---|---|---|
| Part I: What We Found | 1–11 | Research findings on capabilities and outcomes |
| Part II: The Research | 12–15 | Science, psychometrics, survey methodology |
| Part III: Transformation | 16 | Case study of high-performance transformation |
Files
- ch01-accelerate.md
- ch02-measuring-performance.md
- ch03-measuring-culture.md
- ch04-technical-practices.md
- ch05-architecture.md
- ch06-integrating-infosec.md
- ch07-management-practices.md
- ch08-product-development.md
- ch09-making-work-sustainable.md
- ch10-employee-satisfaction.md
- ch11-leaders-and-managers.md
- ch12-science-behind.md
- ch13-psychometrics.md
- ch14-why-surveys.md
- ch15-data-for-project.md
- ch16-high-performance-leadership.md
- conclusion-appendices.md
- accelerate-flashcards.md