Here are 74 books that How to Measure Anything Workbook fans have personally recommended if you like
How to Measure Anything Workbook.
Shepherd is a community of 12,000+ authors and super readers sharing their favorite books with the world.
I’m a software developer turned independent software vendor, learning about product management as a way to launch more successful products. I’m a co-founder of MindMup, a popular collaboration tool used by millions of students and schoolchildren worldwide, and Narakeet, an innovative video maker for people who are not video professionals. The books from this list helped me create successful products that users love, and successfully compete with companies that have several orders of magnitude more staff and resources.
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.
User story mapping is a valuable tool for software development, once you understand why and how to use it. This insightful book examines how this often misunderstood technique can help your team stay focused on users and their needs without getting lost in the enthusiasm for individual product features. Author Jeff Patton shows you how changeable story maps enable your team to hold better conversations about the project throughout the development process. Your team will learn to come away with a shared understanding of what you're attempting to build and why. Get a high-level view of story mapping, with an…
The Victorian mansion, Evenmere, is the mechanism that runs the universe.
The lamps must be lit, or the stars die. The clocks must be wound, or Time ceases. The Balance between Order and Chaos must be preserved, or Existence crumbles.
Appointed the Steward of Evenmere, Carter Anderson must learn the…
I’m a software developer turned independent software vendor, learning about product management as a way to launch more successful products. I’m a co-founder of MindMup, a popular collaboration tool used by millions of students and schoolchildren worldwide, and Narakeet, an innovative video maker for people who are not video professionals. The books from this list helped me create successful products that users love, and successfully compete with companies that have several orders of magnitude more staff and resources.
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.
Whether you're a startup founder trying to disrupt an industry or an intrapreneur trying to provoke change from within, your biggest challenge is creating a product people actually want. Lean Analytics steers you in the right direction. This book shows you how to validate your initial idea, find the right customers, decide what to build, how to monetize your business, and how to spread the word. Packed with more than thirty case studies and insights from over a hundred business experts, Lean Analytics provides you with hard-won, real-world information no entrepreneur can afford to go without. Understand Lean Startup, analytics…
I’m a software developer turned independent software vendor, learning about product management as a way to launch more successful products. I’m a co-founder of MindMup, a popular collaboration tool used by millions of students and schoolchildren worldwide, and Narakeet, an innovative video maker for people who are not video professionals. The books from this list helped me create successful products that users love, and successfully compete with companies that have several orders of magnitude more staff and resources.
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.
Learn to design, build, and scale products consumers can't get enough of
How do today's most successful tech companies Amazon, Google, Facebook, Netflix, Tesla design, develop, and deploy the products that have earned the love of literally billions of people around the world? Perhaps surprisingly, they do it very differently than most tech companies. In INSPIRED, technology product management thought leader Marty Cagan provides readers with a master class in how to structure and staff a vibrant and successful product organization, and how to discover and deliver technology products that your customers will love and that will work for your…
Magical realism meets the magic of Christmas in this mix of Jewish, New Testament, and Santa stories–all reenacted in an urban psychiatric hospital!
On locked ward 5C4, Josh, a patient with many similarities to Jesus, is hospitalized concurrently with Nick, a patient with many similarities to Santa. The two argue…
I have spent most of my adult life using entrepreneurial business practices and principles to redesign and transform nonprofits. From my very first nonprofit organizational acceleration, I was hooked. The wealth one receives from helping other people is so much richer and more satisfying than money–altruism is truly life's greatest pleasure. You know the movie The Sixth Sense where the little kid sees dead people everywhere? I am the same way, except everywhere I look, I see uncaptured opportunities for social impact. I live and breathe social impact strategy, governance, financing, evaluation, and change management. Because by fixing problems in those areas, organizations are able to do more to make the world a better place.
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.
Fully revised and updated, the definitive guide for leaders on how to create lasting organisational change.
Do you remember the last major initiative you watched die in your organisation? Did it go down with a loud crash? Or was it slowly and quietly suffocated by other competing priorities? By the time it finally disappeared, it's quite likely noone even noticed.
Almost every company struggles with making change happen. The 4 Disciplines of Execution: Revised and Updated is meant to help you reach the goals you've always dreamed of with a simple, repeatable, and proven formula. In this updated edition of…
I’ve been working in machine learning for about a decade. I’ve always been more interested in applied than theoretical problems and while blogs and MOOCs (Massive Online Open Courses) are a great way to learn, for certain deep topics only a book would do. I also teach at University of Oxford, University of Birmingham, and various FTSE100 companies. My machine learning has exposed me to many fascinating problems—from leading my own ML-focused startup through Y Combinator—to working at various companies as a consultant. I think there is currently no great curriculum for the practitioners really wanting to apply deep learning in practical cases, so I have given it my best shot.
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!
Now updated with new measurement methods and new examples, How to Measure Anything shows managers how to inform themselves in order to make less risky, more profitable business decisions This insightful and eloquent book will show you how to measure those things in your own business, government agency or other organization that, until now, you may have considered "immeasurable," including customer satisfaction, organizational flexibility, technology risk, and technology ROI. * Adds new measurement methods, showing how they can be applied to a variety of areas such as risk management and customer satisfaction * Simplifies overall content while still making the…
I first learned to program in college in 1970. Since then I’ve spent much time as a software developer, manager, tester, process improvement leader, consultant, trainer, author, and, of course, a user. I quickly learned that I didn’t have time to make all the mistakes that every software developer before me had already made. My training and writing career has involved sharing what I and others have learned with audiences to help them quickly become more effective software development team members, regardless of their project role. This book distills insights and observations both from my own experience and from what I’ve heard from thousands of students and consulting clients.
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.
Corporate and commercial software-development teams all want solutions for one important problem-how to get their high-pressure development schedules under control. In RAPID DEVELOPMENT, author Steve McConnell addresses that concern head-on with overall strategies, specific best practices, and valuable tips that help shrink and control development schedules and keep projects moving. Inside, you'll find:
A rapid-development strategy that can be applied to any project and the best practices to make that strategy work Candid discussions of great and not-so-great rapid-development practices-estimation, prototyping, forced overtime, motivation, teamwork, rapid-development languages, risk management, and many others A list of classic mistakes to avoid for…
A Duke with rigid opinions, a Lady whose beliefs conflict with his, a long disputed parcel of land, a conniving neighbour, a desperate collaboration, a failure of trust, a love found despite it all.
Alexander Cavendish, Duke of Ravensworth, returned from war to find that his father and brother had…
Defining and managing the requirements for a software system is hard! I’ve been interested in improving how projects handle their requirements for more than 35 years. I realized how important this was when I saw how many projects—including my own—struggled and failed when they neglected to build a solid foundation of well-understood and clearly communicated requirements. I’ve personally used nearly all of the techniques described in my book Software Requirements, and I got always better results when I applied those techniques. My books, articles, training courses, presentations, and videos on requirements have been helpful to thousands of business analysts worldwide for many years.
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.
"I spend much time helping organizations capture requirements and even more time helping them recover from not capturing requirements. Many of them have gone through some motions regarding requirements as if they were sleepworking. It's time to wake up and do it right-and this book is going to be their alarm clock."
- Jerry Weinberg, author of numerous books on productivity enhancement "In today's complex, fast-paced software development environment, collaboration-the intense peer-to-peer conversations that result in products, decisions, and knowledge sharing-is absolutely essential to success. But all too often, attempts to collaborate degenerate into agonizing meetings or ineffectual bull sessions.…
Markus Gärtner works as Organizational Design Consultant, Certified Scrum Trainer, and Agile Coach for it-agile GmbH, Hamburg, Germany. Markus, author of ATDD by Example - A Practical Guide to Acceptance Test-Driven Development, a student of the work of Jerry Weinberg, received the Most Influential Agile Testing Professional Person Award in 2013 and contributes to the Softwerkskammer, the German Software Craft movement. Markus regularly presents at Agile and testing conferences all over the globe, as well as dedicating himself to writing about agile software development, software craft, and software testing, foremost in an Agile context.
“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.
Most companies developing software employ something they call "Agile." But there's widespread misunderstanding of what Agile is and how to use it. If you want to improve your software development team's agility, this comprehensive guidebook's clear, concrete, and detailed guidance explains what to do and why, and when to make trade-offs.
In this thorough update of the classic Agile how-to guide, James Shore provides no-nonsense advice on Agile adoption, planning, development, delivery, and management taken from over two decades of Agile experience. He brings the latest ideas from Extreme Programming, Scrum, Lean, DevOps, and more into a cohesive whole. Learn…
Markus Gärtner works as Organizational Design Consultant, Certified Scrum Trainer, and Agile Coach for it-agile GmbH, Hamburg, Germany. Markus, author of ATDD by Example - A Practical Guide to Acceptance Test-Driven Development, a student of the work of Jerry Weinberg, received the Most Influential Agile Testing Professional Person Award in 2013 and contributes to the Softwerkskammer, the German Software Craft movement. Markus regularly presents at Agile and testing conferences all over the globe, as well as dedicating himself to writing about agile software development, software craft, and software testing, foremost in an Agile 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.
Decades of software testing experience condensed into the most important lessons learned.
The world's leading software testing experts lend you their wisdom and years of experience to help you avoid the most common mistakes in testing software. Each lesson is an assertion related to software testing, followed by an explanation or example that shows you the how, when, and why of the testing lesson. More than just tips, tricks, and pitfalls to avoid, Lessons Learned in Software Testing speeds you through the critical testing phase of the software development project without the extensive trial and error it normally takes to…
It is April 1st, 2038. Day 60 of China's blockade of the rebel island of Taiwan.
The US government has agreed to provide Taiwan with a weapons system so advanced that it can disrupt the balance of power in the region. But what pilot would be crazy enough to run…
I have been coding for over 30 years. I’ve seen some miserable interfaces, and some large programs that collapse under their own weight. Software was, at one point, notorious for being late, over budget, and unreliable. These books have helped turn the corner on these failings, and I have found each of them very valuable in my day-to-day programming. While you can learn technique and even languages online, the kind of insight found in these books is rare and worth spending time and money on.
This book changed my entire perspective on writing the UI and UX of great software. Even the revised edition is a bit old but still has many valuable lessons to teach. Platt established many of the fundamental principles of writing usable and transparent software, and his book should be read not only by designers, but perhaps especially by programmers.
This non-technical book discusses the annoyances and dangers we encounter every day when using computers. Written with delightful wit and humor, as well as the insight of an experienced insider, it rips into the design of software much as Atul Gawande's Complications exposed the practice of medicine. Its basic message to ordinary people having problems learning or using their software is this: It's not your fault! It's not because you're dumb! Aimed primarily at casual users of software, the book tells readers what they should expect from their software and how to make their voices heard so that they receive…
