67 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!

“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.

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.

Software engineering involves several phases such as requirements gathering, design, programming, testing, and deployment.

This book explains techniques that allow you to build quality and robustness into every phase of the process. It discusses design, classes, defensive programming, collaboration, refactoring, and more.

The book uses many examples in an assortment of languages but the concepts apply to any programming language. In fact, the main themes like building error detection into every step of the process generalize to even non-programming parts of the development process.

If you’re an experienced developer, you may have discovered some of this book’s ideas elsewhere or even on your own, but you only need to pick up one or two new tidbits to make the book worthwhile.

Exploring requirements is more about communication than computing. Requirements elicitation often involves discussions between business analysts and user representatives or other project stakeholders in either one-on-one discussions or group workshops. Requirements by Collaboration presents a wealth of practical tools and techniques for planning and leading requirements development workshops. It’s packed full of useful tips, checklists, questions to ask, and activities to perform to make workshops effective and successful.

I especially like Gottesdiener’s “collaboration patterns,” eight techniques that a workshop facilitator can employ to help the group achieve its objectives. The pattern called Decide How to Decide is the first one that any group of collaborators should use: exactly how will we make decisions? If you expect to lead, or even participate in, requirements workshops, read this book first.

One way to craft lessons learned is in the form of recommended best practices (or, as I prefer, “good practices”). Best practices represent collected and distilled wisdom from many observers, many projects, and many years of experience. Rapid Development includes 27 best practices for software development, with one chapter devoted to each. Although the book was published more than 25 years ago, most of these are still relevant. Indeed, several of them have been incorporated into routine contemporary practices: evolutionary delivery, designing for change, timebox development, and requirements scrubbing. Techniques such as inspections, miniature milestones, principled negotiation, and reuse are perennially pertinent.