Fifty Quick Ideas to Improve Your User Stories

Topics are covered in a clear way, with very few typos; you get "what has worked" as opposed to "what we think should work" which is refreshing; you also get the impression "devs", "UX practitioners" and such are using experiments to guess the best projects they should be working on, as they are so poorly defined by the business side.They could have made an effort to cover a couple of topics required to understand the gist of the book, to widen its appeal, even if you can find them online. The only negatives are that the authors are so immersed in their topic they have developped their own jargon, so "user stories" mean "system requirements" for everyone else, even if it's important to understand why they use these terms; and no one has "users" but "customers", which has implications for businesses, the narrative and those same "user stories".

Great ideas to make user stories meaningful, point to the real value your users want, and fit into an iteration.I enjoyed the format, which is a lot like software design patterns -- there is a context that describes the problem, a brief description of the solution, and then a section that shows how to apply the solution, along with warnings for when the solution may not be applicable.The book is quite slim, but as I read it I had a sense that the authors had gone to great lengths to cut each idea down to its essential elements. I also got the sense that the experience (evidence) behind each idea is considerably deeper than each brief synopsis might imply. I suppose they could have piled on the evidence and written a much heavier tome, but it wouldn't necessarily have been more convincing because in the end you have to try these out for yourself to see if they will work for you. I appreciated the effort they put into getting right to each point.

There are tons of ideas on how to use user stories in your development process and goes in to somewhat detail on how to implement it. It definitely assumes you are doing some iterative development but my team is doing Kanban so I wish it talked more about how it fits in to that flow based system. It does mention Kanban a few times, however.Overall I found it very useful in figuring out how to break down user stories, apply impact mapping and goals along with user stories, how to measure through rolling average time analysis and T-shirt sizes instead of story points, and comes with examples of how Gojko's teams have done so.

Although I have been writing user stories for over five years, Fifty Quick Ideas to Improve your User Stories augmented my ability to write more descriptive user stories resulting in easier estimation. The second section which discusses Splitting User stories also provided me additional insight into some creative ways that I never thought of. One of the last parts of the book suggests two ways of estimating stories that I never heard of and make sense. I plan to use practically everything I learned from reading this book. I strongly recommend this easy reading book for anyone who writes, splits, and/or estimates user stories.

The book is "OK". I was really looking forward to this book, but I found the writing style challenging at best. There is some very good material in the book, so I'd still recommend it, but at times the authors seemed to ramble or stretch to reach 2 pages for each "quick idea".

Its a good bock that explains in a practical way how to get better results from agility from the use of user stories. It explains very power tool and conceps that today very much companies should consider. For example the validation of outcome with real users, between a lot of other powerfull concepts.

This book came at a perfect moment for our team. We already had some experience with agile methodologies, but we needed some deeper insight to avoid common pitfalls without having to repeat every mistake everybody else made. It paid back more than I paid for it already by page 50, probably even earlier.For some chapters, the title is all you really need to know, but others have surprising insight - not to mention a sure way to win the Asteroids game :)

Very informative and not over the head of someone with little experience in the area.

Comprei o livro querendo saber um pouco mais sobre histórias de usuário mas, no final, eles desconstroem aquela visão clássica de user stories (ainda bem) e acaba indo além. Recomendo principalmente para Products Owners que possuem dificuldade em suas atribuições de priorização.

Quando qualcuno si avvicina al mondo dell'analisi e delle User Story e mi chiede un libro da leggere, suggerisco sempre questo: conciso, pratico e funzionale

Great reference document for scrum masters. I should take another look at it as it holds a few good suggestions that I could apply in real life

This is a really good book that is useful whether you are new to user stories or have years of experience. You might not apply all of the concepts in your current situation but it’s straightforward to assess will I use this, could I benefit from it? Some ideas may be very familiar some not so. There are some great tips and this book is a really good read for anyone irrespective of their role in a team whether that’s BAs, PMs, or Product Managers working with software projects.Each chapter is pretty short often only a couple of pages per concept so it’s easy to read and think about it and then decide whether to continue reading or take and apply the concept discussed.

Es un buen libro para iniciados. No para aprender a redactar ni como manual para seguir.