Strategy, discovery, metrics, growth, pricing, design, delivery and leadership. Each entry says when it is the right one to pick up.
Newport defines deep work as cognitively demanding activity performed without distraction, and argues it is becoming both rarer and more valuable at the same time.
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 …
The authors argue that every hard conversation is really three conversations happening at once, one about what happened, one about feelings, and one about identity.
Krug's short book on web usability, organised around the idea that a page should be self evident and a user should never have to work out what something is. Covers scanning rather than reading, conventions worth keeping, navigation and the home page, and the trunk test for orientation.
A book about product leadership rather than product work. Cagan and Jones argue that the difference between strong and weak product organisations lies in the manager's job of coaching and staffing, and they spend most of the book on those two duties.
Perri names the pattern where organisations measure success in features shipped rather than problems solved, then works through what replaces it. You get a product role defined by outcomes, a strategy framework she calls the …
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 …
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.
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.
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.
Reis and Housley describe the data engineering lifecycle, which runs from generation through ingestion, storage, transformation and serving, with governance, security and architecture cutting across all of it.
An attempt to give software architecture a shared foundation rather than leaving it to war stories. The first part covers architectural thinking, modularity, and the architecture characteristics a system is actually being optimised for, along with how to identify and measure them.