Strategy, discovery, metrics, growth, pricing, design, delivery and leadership. Each entry says when it is the right one to pick up.
Forsgren, Humble and Kim present four years of survey research into what predicts software delivery performance. Four key metrics of deployment frequency, lead time for changes, time to restore service and change failure rate correlate with organisational performance.
Vacanti makes the case for flow metrics over story point velocity. Covers cycle time, work in progress, throughput and their relationship through Little's Law, then the charts that make them usable, being the cumulative flow diagram, the cycle time scatterplot and the histogram.
Cohn treats estimation and planning as separate activities at several horizons. Story points and ideal days, planning poker, velocity, and the mathematics of buffering all get detailed treatment, as do release planning, iteration planning, and the reasons traditional estimates fail.
Produced jointly by PMI and the Agile Alliance as a bridge between traditional project management and agile ways of working. It covers the agile mindset, the selection of a life cycle across predictive, iterative, incremental and …
Huyen's book on building applications on top of foundation models rather than training them. Covers evaluation methodology in depth, prompt engineering, retrieval augmented generation and context construction, finetuning and when …
Frost's methodology for building interface design systems by composing small pieces into larger ones. The stages run from atoms, the smallest elements such as a label or an input, through molecules and organisms to templates and finally pages with real content in them.
The Disciplined Agile handbook, now published by PMI, built on the idea that a team should choose its way of working rather than adopt a named method whole.
Humble and Farley's book on getting software from commit to production reliably. Covers the deployment pipeline in detail, build and dependency management, the testing strategy across levels, configuration management, managing …
Kholmatova approaches a design system as a shared language rather than as a component library, and organises the book around defining that language before building anything.
Kleppmann covers the foundations beneath data systems. Part one covers reliability, scalability and maintainability, data models and query languages, storage engines and encoding.
Huyen treats machine learning as a production systems problem, covering everything around the model rather than the modelling itself. The book moves from framing a business problem as a machine learning problem and deciding …
A condensed statement of the Kanban Method, distilled from Anderson's longer blue book into about eighty pages. It sets out the values, the change management principles and the service delivery principles, then the general …
A comprehensive reference on Scrum covering roles, activities, artefacts and the principles beneath them, written for people who need the whole picture rather than a quick start.
Adzic and Evans give fifty short, independent ideas for improving story practice, each a couple of pages with the idea, why it works and how to make it work. Organised into creating stories, planning with them, discussing them, and splitting them.
The book 37signals wrote about how they built Basecamp, and the direct ancestor of Shape Up. It argues for a smaller product, a smaller team and a shorter path to launch, then works through what that means for scope, design, code and writing.