Goal
The path to "LeanとDevOpsの科学[Accelerate]"
Here is the reading path leading up to this book, derived from its dependencies and ordered from the fundamentals.
The path so far (7 books)
Why read this first: Learning an architecture that controls the direction of dependencies makes you want testing principles that maximize the resulting testability. Unit Testing: Principles, Practices, and Patterns defines what a good test is, converting the loose coupling your architecture enables into testing value.
Sources
Why read this first: Once the small TDD cycle makes writing working tests second nature, you advance to principles of what and at what granularity to test. Good tests are resistant to refactoring, do not get in its way, and reliably catch regressions.
Why read this first: 'The Phoenix Project' lets you experience the chaos of IT operations through a novel, internalizing why DevOps is needed. Once you feel the problem, the royal road is to learn the solutions as systematic practices in 'The DevOps Handbook' by the same author team (Gene Kim et al).
Why read this first: Where 'The DevOps Handbook' surveys broad DevOps practices, Humble & Farley's 'Continuous Delivery' digs into its core—building deployment pipelines—as the original source. Ideal for solidifying the theoretical backbone of CI/CD after grasping the overall picture of practice.
Why read this first: After you can build deployment pipelines from 'Continuous Delivery', you need a yardstick to measure the results. 'Accelerate' shows statistically that CD capabilities predict organizational performance, giving you the rationale to connect technical investment to business metrics.
Why read this first: Once unit tests form a solid base, you stack integration, contract, and end-to-end tests in the right proportions along the test pyramid, scaling up to a system-wide quality strategy. The rule is many at the bottom, few at the top.
Why read this first: Once testing and CI/CD give you a foundation for building in quality, you frame how it affects organizational delivery performance through measurement. DORA's four key metrics show empirically that speed and stability are not a trade-off.