To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyses reviews to verify trustworthiness.
Always love to go back to this book. Jeff’s innovative thinking about the product management process and practical examples of how to adopt his approaches make this a must read for everyone in the tech world.
On page XXIX of the preface is a page that says read this first, which states the book doesn't have an introduction. The preface then continues for another 15 pages to page XLIV before chapter 1 starts. The technique of story mapping is very interesting and one I'll be using on a large project I'll be working on in the future. The way in which business stakeholders define what to them constitutes the MVP is interesting and also worth trying. The rest of the book however seems to be promoting stories over requirements. I can't call it a discussion as it does not go into any detail of the advantages and disadvantages of either approach across a variety of situations. The book makes some salient points that I agree with such as most companies not useing user stories correctly, but my personal opinion is you could remove 50%-60% of the content of this book and it would still convey the same message.
Some books are written just because the author has been reading other similar books or wants to gain some authority in the field for better clients etc and there is nothing wrong with this. I read 30% of it and nothing new, original is conveyed through this it although the introduction promised big some things to come. If you’re not a novice in UX industry, don’t buy this book. You better watch some cartoons on TV.
I found the first two thirds witty, well paced and insightful into the difference between collecting requirements and co-developing a shared understanding of a business solution. The last third, I got quickly bored, it was too dense and jargonny, and felt a bit like filler. I think the point is user story mapping is only the beginning, in and of itself, it is not a solution. So, that's where actual development frameworks like DevOps, Scrum, Kanban come in.
Patton's writing style seems to make this book seem disjointed - I felt that I'd got something out of the first read-through but it was only on the second time through that I realise how good it really is. Do the same and you won't be disappointed. This is a much-neglected aspect of user stories and one that helps tie the subject together in a way that makes sense.
Really opened my eyes to how you need to be aware of how a user story can effect other areas of the system you are working on. Really great read. I would highly recommend it if you are an expert or a beginner.