User Story Mapping: Discover the Whole Story, Build the Right Product
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 you
In general, the content is great. The knowledge that's getting passed to the readers is well served & valuable. The content is well illustrated & clear. But all of that gets really annoying, because the book is just too wordy. Quite quickly I got the impression (and I couldn't get rid of it until the end) that I'm reading the same stuff again - even if it's smart & applicable, it gets annoying.
What are my favourite parts / chapters?
* about how requirements are supposed to ...more
However, it's still a really good book on User Stories, Agile development, and Lean Startup mentality. If I had started reading this book with ...more
It's highly recommended if yo ...more
• is a way of talking about who does something, what it is, and why they do it. It also helps us prioritize and agree on the most important paths users need to take, which helps us make decisions down the line
• is used to build shared un ...more
User story mapping is a valuable tool for software development. This often misunderstand technique can help your team stay focus on users and their needs without getting lost in the enthusiasm for individual product features. The main goal of using stories is shared understanding. Story mapping is very simple, but it is not easy!
Who should read this book?
Book could be useful for product manage ...more
You should get this book if you're an entrepreneur or business person with no tech background and wonder:
- How much should I know about software to work with technology?
- How the heck do I translate my product vision, business model or strategy into working software?
- What does a tech/product team look like?
- What other books might I read to go deeper?
A brilliant journey awaits you at the other side. ...more
Lots of examples, practical insights, it is clear the author spent a lot of time working on a software at different roles. It is written in a very friendly tone, just like you're having a conversation with a more experienced colleague. I've already tried several ideas from the book at work and plan to grab more of them. ...more
5 star - It's so useful for me that I'll probably get back to it soon after, in order to apply the information.
4 star - It's good, worth reading, but if I don't actually apply the information I'll forget most of it.
3 star - Some good parts, but has some major flaws I could not get over.
2 star - Appreciated the effort for a while, but then I burned it in my basement laughing like
1 star - I literally ...more
Some of my key takeaways:
- Focus on the users, not the product. Minimize output, maximize outcome.
- The "minimum" in MVP refers to what's the minimum acceptable for the user, not for you, the developer.
- User stories are meant to start a conversation with your team. It's not a memo or a requirements document.
- Software development is iterative. Iteration is natural, and should not be treated as a failure.
- A good development process is ...more
Good book, good random ideas about the overall process of product development, but disorganized and bloated.
The first half of the book felt like it's therr to increase the page count. One can tell if the author is writing in a slow pase on purpose. He tried to make too many little jokes, and the writing style was too relaxed. That, and I don't really remember getting anything from if.
The first part deserves 2 stars, the second part gets 4.
In the end, although ...more
It was a pleasant surprise, because it doesn't talk just about the Story Mapping technique, but a whole way of dealing with stories, SW projects, an experimental and learning mindset through discovery processes.
So it was worth reading it, it's easy read and understand and a fast reading book. I'd suggest it to Agile Coaches and especially PO's.
I think it lacked writing a bit more d ...more
It's rare to find a book you truly find both useful and interesting to read from cover to cover and Jeff Patton does a terrific job to keep building up interest and maintain great continuity throughout the book, pointing out useful references to specific points in previous chapters, highlighting key concepts and reminding of you of things you've read so that with the current material they make more sense.
As a seasoned developer and agile practitioner, this book h ...more
Short, witty and to the point. Oh, and videogame metaphors. Need I say more?
Yes, it's wordy and repeating the same stuff over and over, but it's utterly useful. It's more of a collection of stories from the trenches about user stories. It'll help you understand that you don't have to reinvent the wheel when it comes to communication & collaboration practices. People have been practicing methods which encourage agility (but not necessarily Agile™) effectively and systematically for quite a few y ...more
As one caveat, I really wish this author would have included more diverse perspectives. I don’t think he cites a single non-white male in his work. This is of course both a symptom of and cause for the continuing problems of inequality in tech ...more
-One chapter praised the doctor patient relationship present in medicine and Patton postulated that software development should work akin to it. That somewhat put me off; I think most general practitioners only have very superficial knowledge; I'd much prefer them just giving me the specific prescription that my research concluded that I need :-P ...more
Goodreads is hiring!
Learn more »