Scan barcode
Reviews
User Story Mapping: Discover the Whole Story, Build the Right Product by Jeff Patton, Peter Economy
ditorelo's review
5.0
I've learned a lot from this book. Nothing too new as far as "thinking Agile" goes, but the techniques discussed by Patton are eye opening. The user perspective changes conversations greatly too!
voldie's review against another edition
2.0
Good propaganda book on creative uses of sticky notes. By this book you will probably not understand more or learn new stuff. But you will be totally willing to stick aforementioned notes on every wall of yours.
dayirisbarrios's review against another edition
4.0
I enjoyed reading the book. I liked the examples and info provided. Good illustrations to deliver the message and concepts. I felt the last chapters as well as some concepts were very repetitive.
shiftyteeth's review against another edition
3.0
Was really hoping for more of a hands on / workbook approach. There is a great early exercise in the beginning but that approach was abandoned for more generic excerpts and half stories from seasoned developers. A good read and a nice refresher but a bit long for what it delivers.
parkershepherd's review against another edition
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 against another edition
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 against another edition
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 against another edition
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
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.