Accelerate
The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations
Nicole Forsgren, Jez Humble, and Gene Kim · 2018 · Technology
13 min · 12 chaptersNarrated in your voice
What it's about
Drawing on four years of survey data from thousands of technology professionals, the authors argue that software delivery performance can be measured rigorously and that a specific set of technical, process, and cultural capabilities causally drives it. They show that speed and stability are not opposing goals, and that firms which excel at both outperform competitors on profitability, market share, and employee wellbeing. The book replaced folklore about IT performance with statistically validated evidence.
Read a little every day
15 min a day
1 days · done Sat, Oct 31
Read together
Start a circle and share the code — everyone sees everyone's honest place in the book. Accountability, not leaderboards.
Who it's for
- Engineering leaders who want evidence, not opinion, for how to invest scarce improvement effort - Product and operations executives deciding whether DevOps investment actually pays off financially - Researchers and consultants who want a rigorous methodology for studying organizational and technical performance together
What’s inside
- 1Measuring What Actually Matters1 min
Technology performance can be quantified with a small, validated set of metrics, and organizations that refuse to measure it are managing blind.
- 2The Four Metrics of Delivery Performance1 min
Software delivery performance reduces to just four numbers: deployment frequency, lead time for changes, mean time to restore service, and change failure rate.
- 3Dismantling the Speed-Versus-Stability Tradeoff1 min
Speed and stability move together rather than trading off against each other, so slowing down deliberately to be safer is usually a mistake.
- 4The Technical Practices Behind Continuous Delivery1 min
A specific bundle of technical practices, especially trunk-based development and automated testing, is what makes frequent low-risk deployment possible, not heroics or better people.
- 5Architecture That Lets Teams Move Independently1 min
Loosely coupled, well-encapsulated system architecture is a prerequisite for high delivery performance, because tightly coupled systems force coordination overhead that no amount of process improvement can fix.
- 6Lean Management and Small Batches1 min
Working in small batches and limiting work in progress, borrowed from lean manufacturing, is what actually enables fast feedback in software, not simply asking teams to work faster.
- 7Generative Culture and Psychological Safety1 min
An organization's culture, specifically whether information flows freely and failure is treated as a learning opportunity rather than a blame target, predicts delivery performance as strongly as its technical practices do.
- 8Leadership's Role in Enabling Capability1 min
Transformational leadership, specifically leaders who articulate vision and provide intellectual stimulation, sets the ceiling for how far technical and cultural improvements can go.
- 9From Delivery Performance to Business and Human Outcomes1 min
High software delivery performance causally improves organizational profitability, market share, and productivity, and also reduces employee burnout, making the earlier capabilities a business and human imperative, not just an engineering preference.
About Nicole Forsgren, Jez Humble, and Gene Kim
Nicole Forsgren, PhD, co-founded DORA and led the State of DevOps research before roles at Google and Microsoft Research. Jez Humble co-wrote the earlier book Continuous Delivery and worked as a software engineer and consultant across large-scale systems. Gene Kim founded the security firm Tripwire and wrote The Phoenix Project, and runs IT Revolution, which studies high-performing technology organizations.
