I found it interesting and useful. The book well describes the essentials of user stories and application of it. The examples are given from the the perspective of customer vs development team. To me, the missing part is model when the development team is also an owner of a product they create.

A quick read on using stories in software development. Very high level. While I read it cover to cover, I would advise reading the end of each chapter's bullet points to see what parts you wish to read more about. Bullet points pretty much tell you everything you need to know.

This was my intro to the Agile process, and I read it with with the rest of the team at the start-up where I was working at the time, so I may not be separating the book from the experience here. We had developers, product managers & sales engineers go through the process of modeling users; and defining, scoring and prioritizing stories. Regular updates from the daily scrums kept the rest of us in the loop, and our next several release cycles were better than the previous ones:

- we shipped what we said we would, close to when we said we would
- we shipped features to meet goals that the entire team bought into (or at least understood)
- better communication meant everyone was on the same page

Had I read it in a vacuum, w/o a specific project to work on, this book may not have been as valuable to me. I still use what I learned during this experience.

Decent book by Mike Cohn about user stories. Since we are applying SCRUM for the development process in our tiny company and I had no prior knowledge to SCRUM nor user stories, this book seemed like a good primer introducing me in those concepts.

I was right. Don't expect any ground breaking or world moving theories here. Just a very clear and thorough explanation of what user stories are, what user stories are not, how they relate to alternative requirement gathering strategies and how to use them in practice.

What I like is that the book can be read at different levels and from different user roles or perspectives. You can read it as a beginner (first part of the book) but also for the expert there is more than enough useful information justifying a purchase.

If you are into agile (software) development, you need a book about user stories (or a list of bookmarked blogs if you are not in the whole paper thing). I suggest this book as candidate number 1.

Arranged like a textbook with questions answered in an appendix, this includes a historical arc of Agile from the innovations of Extreme Programming (XP). The User Story focus is weighted toward the physical collateral (index cards, etc.) and face-to-face collaboration on development, including thought-provoking, imaginative peronae writing. This is a very good, gentle introduction to the technique.

When I started working at the scrum team, I was searching for a book that could give me a good understanding of the user stories concept. I needed some theory and a lot of examples. This is exactly what I found in User Stories Applied. It is very well structured and very practical. I was able to implement its recommendations right after reading the first chapter. I would recommend it to anyone who is new to agile.

This seems to be one of the classic texts on user stories. It is generally quite well-written and organized with copious examples and a several-chapter case study at the end. It gives a clear understanding of user stories, what they're for, what they're not, how to write them, how to prioritize them, and how to organize them into iteration planning and final testing.

The book has a couple downsides. First, my copy cost 41 Euros, which is at least twice as much as it should have. It's a print-on-demand book from 2004 with around 250 pages - the cost is extortionate. Second, it's somewhat dated. It assumes the reader will be coming out of a waterfall development mindset and does a lot of explanation of Agile and arguments on its behalf. It also seems to have been written before product management orgs reached their current status as a major component of most software companies, so the function is rarely mentioned and not much considered. And some of the terminology is a bit dated - what we would call jobs-to-be-done these days is called Goal Stories, for example. Third, stylistically, the writing is at times a bit odd. I have several examples, but the one I'll mention is that what most people would call "red flags," Cohn calls "smells," which I found a bit weird.

Modern readers might blanche at the price, need to skim the stuff on why scrums are good, and translate references to customer teams into product manager equivalents, but at the end of the day, you get what you came for - a solid, comprehensive overview of the topic.

After reading this book you can say to have a complete view of User Stories. I have to say that this book was a little boring in the writing. I read another important book by Cohn which was Succeeding with Agile: Software Development Using Scrum and I read it with more pleasure.

I really appreciate the real worl example in the end and the Appendix about Extream Programming

스토리는 스크럼 프로세스에 있어서 가장 중요한 요소 중 하나다. 스크럼을 운영해온지 5년이 지난 지금까지도 모든 팀원들이 같이 이야기할 수 있는 스토리를 작성하고 운영하는 것은 어렵다. 좀 더 실전적이면서도 명확한 프랙티스를 이책을 통해 얻을 수 있었다. 같이 일하는 기획자들에게 애자일프로세스를 교육하고 성장시킬 때 유용한 서적인 것 같다. 여기 있는 대로 프로세스를 진행하는 것도 좋지만 몇가지 좀 더 효율적인 방안으로 수정해서 진행할만한 요소들이 있고, 그 또한 하나의 팀으로 업무를 진행하면서 느끼게 되는 다양한 재미 중에 하나다. 레퍼런스로 앞으로도 두고두고 살펴볼만한 책인것 같다. 지금 돌이켜보면 대학원에서 소프트웨어 공학을 전공할 때만 해도 지금과 같은 애자일프로세스가 아주 많이 활성화되지는 않았을 때였다. 지속적으로 요구사항 분석 및 소프트웨어 개발 프로세스가 애자일 프로세스로 정리되어 가는 모습을 보면서 실제로 계속해서 운영할 수 있는 기회를 가질 수 있었던 것은 정말 감사한 일이다

Dig very much down into user stories, but just part one seems enough to know what they are, everything else is the matter of managing product development process which applies user stories, not really about the user stories themselves.

Re-reading this not so old classic. It is amazing how many things are now obsolete, but it keeps its essential value as the bible for user stories (that probably only covers a third of the book!)

Was hoping to learn about agile development, but this focuses on user stories as used within agile development. Not useful for me.