Accelerate The Science of DevOps
One book, placed in its field — what Nicole Forsgren, Jez Humble, Gene Kim's book gets right, where it goes further than the rest, and what the rest of the field adds.
Mike West, Editor · Leading With Data · softwareengineeringprofessional.com/guides/profile-accelerate-the-science-of-devops-nicole-forsgren-jez-humble-
Arrow keys or swipe to move · N for notes · F for full screen
Accelerate The Science of DevOps
One book, placed in its field — what Nicole Forsgren, Jez Humble, Gene Kim's book gets right, where it goes further than the rest, and what the rest of the field adds.
Mike West, Editor · Leading With Data · softwareengineeringprofessional.com/guides/profile-accelerate-the-science-of-devops-nicole-forsgren-jez-humble-
The problem
Software delivery performance erodes when it is left to instinct instead of method.
You were taught the moves piecemeal, never the whole model.
Accelerate The Science of DevOps · Mike West, Editor · Leading With Data
The model
- 01Continuous Delivery
- 02Comprehensive Version Control
- 03Test Automation
- 04Trunk-Based Development
- 05Shift Left on Security
- 06Loosely Coupled Architecture
- 07Empowered Teams / Tool Choice
- 08Lean Management Practices
Accelerate The Science of DevOps · Mike West, Editor · Leading With Data
Step 1 of 5 · Continuous Delivery
CD is a state of the system (always deployable), not a frequency of deployment.
Misconception
Continuous Delivery means deploying to production continuously, so you don't need it unless you release many times a day.
Reality
CD is about keeping software in a releasable state at all times and making deployment a low-risk business decision; the deploy cadence is a choice, not the point. You benefit even if you release monthly.
Accelerate The Science of DevOps · Mike West, Editor · Leading With Data
Step 2 of 5 · Comprehensive Version Control
Comprehensive means code plus configuration plus scripts plus infrastructure definitions—all four.
Misconception
We use Git for our application code, so we have comprehensive version control.
Reality
The predictive power comes specifically from versioning system configuration, build scripts, and infrastructure definitions—not just app code. Configuration in version control matters more for delivery performance than application code being versioned.
Accelerate The Science of DevOps · Mike West, Editor · Leading With Data
Step 3 of 5 · Test Automation
Reliability of tests matters more than quantity: green must mean releasable.
Misconception
More test coverage and a dedicated QA team writing tests will improve our delivery.
Reality
The research finding is that tests must be reliable (a pass means releasable, a fail means real) and primarily written and maintained by developers. Tests owned by a separate team correlate with worse outcomes, not better.
Accelerate The Science of DevOps · Mike West, Editor · Leading With Data
Step 4 of 5 · Trunk-Based Development
Fewer than three active branches and daily merges to trunk is the empirical high-performer pattern.
Misconception
A rich branching model like Git-flow with release branches and feature isolation is a sign of engineering maturity.
Reality
High performers use fewer than three active branches, merge to trunk at least daily, and avoid code freezes. Elaborate branching structures correlate with lower delivery performance, not higher.
Accelerate The Science of DevOps · Mike West, Editor · Leading With Data
Step 5 of 5 · Shift Left on Security
Security integrated across the lifecycle predicts higher CD; a downstream security phase predicts friction.
Misconception
Shifting security left means adding a security scan step to the CI pipeline and calling it done.
Reality
The predictive practice is integrating infosec into design, development, and operations with feedback at each stage—plus preapproved, easy-to-use libraries and tooling that make the secure path the easy path. A scanning stage is a fraction of this.
Accelerate The Science of DevOps · Mike West, Editor · Leading With Data
A framework to use
The 24 Capabilities Model for High Performance
This framework is part of the full guide. See the guide →
Accelerate The Science of DevOps · Mike West, Editor · Leading With Data
The cheat sheet
- Continuous DeliveryCD is a state of the system (always deployable), not a frequency of deployment.
- Comprehensive Version ControlComprehensive means code plus configuration plus scripts plus infrastructure definitions—all four.
- Test AutomationReliability of tests matters more than quantity: green must mean releasable.
- Trunk-Based DevelopmentFewer than three active branches and daily merges to trunk is the empirical high-performer pattern.
- Shift Left on SecuritySecurity integrated across the lifecycle predicts higher CD; a downstream security phase predicts friction.
- Loosely Coupled ArchitectureThe measurable outcome is independent deployment and testing without cross-team coordination.
- Empowered Teams / Tool ChoiceTeam-level tool choice, grounded in users and the work, predicts higher delivery performance.
- Lean Management PracticesExternal change-approval boards slow you down without improving stability—use lightweight peer review instead.
Accelerate The Science of DevOps · Mike West, Editor · Leading With Data
Sources
- Accelerate The Science of DevOps — Nicole Forsgren, Jez Humble, Gene Kim
Accelerate The Science of DevOps · Mike West, Editor · Leading With Data