User Story Mapping

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.

An good brochure on user stories that could fit in 3-5 medium posts;
some of the examples are silly and full of nonsense details which at times makes you wanna stop reading it;
yes, it explains a couple of organizational things - how to assemble work groups, how to set priorities and how to plan your backlog on a theoretical level.

The thing is (and it often applies to other books on the topic) - you never get to hear about some interesting startups killing it out there with agile. Most of time these are some no-name companies supposedly achieving great successes;

question is - where are these now? and another one - when working with a village project with dated technologies in the US (let's admit, 90% is far behind Silicon Valley or even Europe at times. My pal was dictating his credit card number via phone because in some places that's how US operates these days).

if we look at mediocre companies no one has heard about - I would take it with a grain of salt and pepper as there is no way to tell the user story mapping was even implemented there for good.

This is the best User Story Mapping book I've read. It's also the only User Story Mapping book I've read.