Ratings9
Average rating3.8
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 exercise to learn key concepts quickly Understand how stories really work, and how they come to life in Agile and Lean projects Dive into a story's lifecycle, starting with opportunities and moving deeper into discovery Prepare your stories, pay attention while they're built, and learn from those you convert to working software
Reviews with the most likes.
The title of the book did not imply that this book also actually covers how to write good stories, and gives an overall picture how to start and how to deliver the end result from an agile perspective (which are presented well enough). If you are already familiar with those topics and are actually looking to delve more in-depth into user story mapping (with great examples), then this might not be it. It also repeats itself sometimes. I get that some things bear repeating, but still, it's a bit much.
The author explains a lot of interesting stuff about product discovery. My only gripe with this book is the tone of the author. It is too playful to consider this book serious (although the book has some very serious stuff)
I would recommend this book to product managers, Senior Developers, engineering managers, and their coaches.
This book narrows in on user stories and connects to the process around them.
It is not about how stories shall be written. But how to use them, what's the purpose and how to make the most of them.
A couple of key points
* It's not about what's written on them it's about the context they provide.
* “Stories are Actually Like Asteroids” - Ie breaks them down into smaller stories but not all at once.
* It is all about the user and discovering what is needed.