66 books like How to Measure Anything Workbook

Patton’s book is an amazing introduction to modern product management techniques, both from a practical and theoretical view. It introduces story mapping as a practical technique that you’ll be able to use immediately to start making sense of large plans and visualizing product ideas. More importantly, Patton uses this technique as an excuse to introduce readers to principles such as focusing on outcomes over outputs, working closely with users and iterative delivery, and experimentation. 

The book is a gateway drug for new product managers. It is an easy read and will get you hooked on modern ways to ensure that both users and stakeholders get value from your products. It helps people get started easily in a new role and provides a great foundation for going deeper into this field.

Other books will teach you to focus on outcomes, but then the next question is what kind of outcomes are worth focusing on. This is where Lean Analytics comes in. The real gem from this book is the model of Five Stages of Growth, suggesting a typical progression of outcomes that product managers should follow when growing a product from an idea to a marketplace winner. It’s an invaluable thinking tool for new and experienced product managers alike. In addition, the book documents what kind of metrics various successful products tracked throughout growth, and provides some amazingly useful reference values for key business metrics for different categories of software products.

This book is great as an introduction to business metrics for new product managers, focusing specifically on software products. I recommend reading this before any other metrics book, as it’s very practical and relatable.

Cagan’s book is a deep dive into the principles of modern product management. It expands on the theoretical ideas that Patton introduces in User Story Mapping, and provides many additional tips for engaging customers, experimenting with product ideas, and tracking outcomes. In addition, it deals with the organizational side of product management, so it will be valuable to people working for larger companies that need to manage staff and set up company-wide processes.

Reading this book will help you expand your views of product management, and add lots of additional tools to your thinking process.

Planning is easy, but execution is hard. Nonprofit leaders can gain a clear, practical understanding of how to measure and execute an organization's progress toward social impact goals with the clear, simple, and compelling four disciplines of execution.

It is simply terrific for putting strategy into practice. You will learn the key concepts from 4DX. We found reading it like getting a new set of glasses that brings the world of management into focus and allows us to see a pathway to success.

While technically not about deep learning, this book is fantastic for those interested in pursuing applied or practical machine learning problems. While the central thesis of a topic can be reduced to “Frequently, models are valuable simply by reducing uncertainty,” it is definitely worth a read as there’s a lot of deep thinking in this book!

Many agile projects employ user stories as a way to represent requirements rather than a more traditional approach combining use cases and functional requirements. I favor the latter approach for several reasons. Nonetheless, user stories are well established in the agile development world, and if you wish to learn about them, there’s no better author to read than Mike Cohn. Cohn describes how to craft user stories well and how they fit into the agile development process.

“Good agile testing is good context-driven testing applied in an agile context.”

I recall reading through the authors’ lessons on software testing at about the same time I dived into more agile topics. Lessons Learned in Software Testing helped me keep the connection towards more traditional contexts – more so since I was still working in a more traditional context.

With their more than 100 lessons some of them applied to me, others did not. I am sure, other readers will find the same in their context.

“Good agile testing is good context-driven testing applied in an agile context.”

The authors of this book summarize their decades of experience in software testing in over 100 lessons they learned. Follow them along different aspects of the tester’s job, as they re-tell various stories collected over the years with some clear guidance to surviving and testing project.

These software testing industry leaders have some timely contextual advice in here – whether you work as a tester on an agile team or in a more traditional fashion.

This book helped me set my initial approach to software development and I still periodically return to it for grounding.

An MIT project theorized that new-fangled PC software developers knew something mainframe and mini-computer makers didn’t. MIT’s research revealed something else entirely: Microsoft had uniquely effective ideas on how to build complex products in rapidly evolving competitive markets. Here is “agile” before it was put into the Manifesto in 2001, in a more complete form. Ever wonder where the idea of a team comprising functional specialists with overlapping roles, united by a common goal, came from? Or incremental feature evolution with periodic synchronization and constant testing? Early brilliance still of foundational relevance, in a coherent and engaging form.

Many of the most significant principles of effective software development are timeless. They’re independent of the development life cycle or model, programming language, application type, and so forth. Although this book is quite a few years old now, nearly all of its contents are still valid. The 201 principles cover the full spectrum of software engineering: general principles, requirements engineering, design, coding, testing, management, product assurance, and evolution. The descriptions of each principle are concise, whereas my 60 lessons in Software Development Pearls go into a great deal more detail and offer many practical techniques.

There’s an unfortunate tendency among young software people to disregard knowledge from the past as irrelevant to them. That’s not correct. This book can help close significant gaps in any practicing software developer’s knowledge.