User Story Mapping

One of those books that could have been a long article.

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.