Strategy, discovery, metrics, growth, pricing, design, delivery and leadership. Each entry says when it is the right one to pick up.
The seventh edition moved away from the process groups and knowledge areas of earlier editions and reorganised the guide around twelve principles and eight performance domains.
An accessibility book organised around design decisions rather than around compliance checklists. The first part introduces personas covering people with different abilities and situations, including screen reader users, people …
The fourth edition of the book that introduced personas and goal directed design to a wide audience. Its first part covers the process, moving through research, modelling users into personas, deriving requirements from scenarios, and framing an interaction design solution.
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.
Kalbag covers the ground a team needs in order to start taking accessibility seriously, from the legal and business context through to specific implementation guidance.
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 …
Pichler's early and still useful book on the Product Owner role. Covers what the role actually involves, envisioning the product, working with the product backlog, planning releases, and collaborating in sprint meetings.
Derby and Larsen give a five stage structure for retrospectives covering set the stage, gather data, generate insights, decide what to do, and close. The bulk of the book is a catalogue of activities for each stage, with timings, materials and the situations each suits.
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 …
Larson treats engineering management as a systems problem. Covers team sizing and the four states a team can be in, how to run an organisation through growth, technical migrations, career ladders and performance calibration, and …
Greever addresses the conversation that happens after the work is done. Covers understanding who the stakeholders are and what they actually respond to, listening properly before responding, and the specific structure of a …
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.
Fadell's book draws on the iPod, iPhone and Nest, organised as short chapters of advice covering an individual career, building a team, building a product, building a business, and being a chief executive.