Scan barcode
parkershepherd's review
3.0
User Story Mapping shows some clear strategies for breaking huge complicated projects into a clear, lean plan. Some of the concepts like thinking of documentation as a "vacation photo" (meaningful to someone who was there, but not to someone who wasn't) has changed how I communicate throughout the lifecycle through new projects.
The advice in the book is great and the framework provided is very useful, but it is too long winded and repetitive to easily recommend to just anyone unless they're already frustrated with the problems the book tackles.
The advice in the book is great and the framework provided is very useful, but it is too long winded and repetitive to easily recommend to just anyone unless they're already frustrated with the problems the book tackles.
mugunthkumar's review
4.0
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)
four_sharks's review
3.0
This book would be great for someone who doesn’t work in tech and isn’t familiar with facilitating groups of stakeholder conversations. If you do work in tech already you might be waiting for a bit of knowledge that you didn’t have already when you read this book. User story mapping is very easy to do and only takes about one page of reading to understand it. The fact that this is a book means you can skim a lot and still get the idea. I think I was waiting for some kind of major insight on how to understand customers- nope.
noeminoeminoemi's review
2.0
It is enough to read the introduction of the book, where the author lists all the agile developing principles that he's later thoroughly explaining. He tells in too many details the way he reached to those principles.
I did not like that he writes same way he probably talks. I'd listen to those jokes, but not read them. It seemed a time-waster to me.
That's why I gave up the book after the first 35 pages.
I did not like that he writes same way he probably talks. I'd listen to those jokes, but not read them. It seemed a time-waster to me.
That's why I gave up the book after the first 35 pages.
bizlet's review against another edition
3.0
The ideas are helpful and I agree with other reviewers that it just had too much fluff/repetition.
I also had no idea how to take the ideas in this book and apply it in real life without the team size to back it up or an advocate to push these ideas through to the end. In all of the discussions of what kinds of conversations to have there wasn't a mention (that I saw) of what it takes to coordinate that kind of work.
My assumption is that the author has a blind spot for the critical role someone like him plays when working with a team to collaborate on handling projects the way he advocates handling them in the book.
So it was great to see all of these teams doing a wonderful job and at the same time, terribly demoralizing and made me feel like there's a utopia where stakeholders and developers are ok getting pulled into a hundred conversations in a week with the added time of prep work and cleanup from those discussions.
Also, a lot of these concepts are great if you're in the same room. I work remotely (even before COVID19) and am used to books ignoring the fact that not everyone works in the office.
I also had no idea how to take the ideas in this book and apply it in real life without the team size to back it up or an advocate to push these ideas through to the end. In all of the discussions of what kinds of conversations to have there wasn't a mention (that I saw) of what it takes to coordinate that kind of work.
My assumption is that the author has a blind spot for the critical role someone like him plays when working with a team to collaborate on handling projects the way he advocates handling them in the book.
So it was great to see all of these teams doing a wonderful job and at the same time, terribly demoralizing and made me feel like there's a utopia where stakeholders and developers are ok getting pulled into a hundred conversations in a week with the added time of prep work and cleanup from those discussions.
Also, a lot of these concepts are great if you're in the same room. I work remotely (even before COVID19) and am used to books ignoring the fact that not everyone works in the office.
miguel_ocana's review
4.0
Merece la pena aprender la técnica, y aclarar definitivamente qué es y qué no es una historia de usuario. Aunque en ocasiones se hace repetitivo, consigue dejar claro la importancia de virar toda la organización para centrarse en los resultados
chrisjm's review against another edition
4.0
A great book if you need a crash course on how to do story mapping. Includes a multitude of case study-like stories, strategies, anti-patterns, and lots of helpful explanatory diagrams and drawings.