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.
Cutler's collected writing on the feature factory pattern, where teams ship features on a schedule with no feedback loop to outcomes. Covers the signals that you are in one, including no discovery, success measured at delivery, and constant context switching.
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 …
Thomke studied experimentation programmes at companies including Booking.com, Microsoft and Amazon, and wrote about what turns testing into a capability rather than an occasional activity.
Croll and Yoskovitz work through which metric matters at which stage for six business models covering ecommerce, SaaS, free mobile apps, media, user generated content and two sided marketplaces.
Nandakumar wrote this for the gap between a business idea stated in one sentence and a product a team can begin. The method runs from naming the business outcome, through the impact the product would have to have and the measures …
Doerr's account of Objectives and Key Results, drawn from Intel and applied at Google and elsewhere. Objectives are qualitative and directional while key results are numerical and time bound.
Wheelan explains the statistical ideas that turn up in ordinary working life without asking the reader to do much of the maths. Chapters cover descriptive statistics and what an average conceals, correlation, basic probability …
Niven and Lamorte wrote the implementation manual for OKRs rather than the argument for adopting them. The book covers writing objectives and key results that hold up under scrutiny, the difference between committed and …
A brief book built on one distinction. Output is what you build and outcome is the change in human behaviour that follows. Seiden gives three questions for defining an outcome, describes the Magic Machine exercise for connecting …
A beginner's guide to SQL built around real public datasets rather than toy tables. It starts with creating and querying tables, then works through joins, aggregation, subqueries, common table expressions and window functions using census, taxi trip and food inspection data.
Rodrigues works through the analytical toolkit for consumer products, from defining metrics to building models that explain user behaviour. The book starts with behavioural theory and the argument that a metric needs a causal …
Perri and Tilles describe product operations as a discipline with three pillars, which are data and insights, customer and market insights, then process and governance.
A statistics book aimed squarely at people who run user research, organised around the questions that actually come up in the work. It covers confidence intervals for completion rates and task times, comparing two designs, sample …