It answered on many questions I collected over the years by writing stories in a very simple manner.

Here are my top findings:
- Stories should be as a slice of a cake. Story should fit in the sprint and should include all layers of the application;
- Story should be closed with an achievement;
- Keep the UI Out as Long as Possible;
- Keep user stories short, and don't forget their purpose as reminders to hold conversations;
- INVEST story principals: independent, negotiable, valuable to the user, small, testable.
- Accepting Responsibility. At the end of an iteration no one can say "I finished my work, but Tom still had a few tasks left.

I have read some of the materials from the web regarding user stories, best practices of how to best write a user story... And I was so confused. I could not explain the benefit from all those writing or concept.
When I read the User Stories Applied book, It opened my eyes, clear my thoughts. I suddenly feel the value of the user story. And most importantly, I know what it is and why I need it.
One of the core ideas I love from his book are parts composed a user story:
Card (story)
Express the story, the business value
Conversation
Here is the interesting part, where it said that use story encourages conversation, discussion. It is not a contract or fixed requirement.
Confirmation
Referred as Acceptance Tests.

I would recommend this book for anyone who wants to learn about "User Story".

¿Qué es una historia de usuario?¿qué elementos debe cumplir?¿cómo se crean?

El libro User Stories Applied de Mike Cohn nos da respuesta a éstas y cualquier otra duda que tengas acerca de las historias de usuario. Una visión completa de una de las herramientas clave que se utiliza en todo el ciclo de vida Agile. Sea cual sea tu conocimiento sobre las historias de usuario, no te puedes perder este libro.

Encontrarás un completo resumen del libro en español en este artículo:
http://bit.ly/2sJvYmU

Great book for those wanting a deep understanding of all the ins and outs of user story methodology. Book covers estimation, detailed business examples and comprehensive comparison to other approaches like use cases / XP. Also includes many exercises to test your knowledge. Have a ton of highlights and bookmarks which I use regularly now. Must read for anyone building or running software projects.

Nice book but pretty outdated.

Key takeaways:
1. A good user story follows this formula: As a (user), I can (activity), so that (reason why).
2. Keep stories small and easy to estimate.
3. You can make an epic if you need a lot of stories for an overarching goal.
4. Personas can be useful but not always necessary.
5. Add constraints or tests on the back of cards (and success criteria).

User stories very well explained. Read the epub version but wish I had the paperback on my desk at work for easy reference.

Although somewhat out of date in many respects, this book still provides a good overview of why and how to write user stories. Given that the book was first written almost 20 years ago, we can forgive most of the outdatedness. For example, I don’t think most Scrum teams use 30-day sprints anymore, and many many teams are now remote - even before COVID-19.

The core material, however, remains valuable, particularly for readers more accustomed to something heavier than user stories, or for those of us who need a refresher on user modelling or vertical slices of functionality.

I wished the book had more advice on non-functional stories and, perhaps, an update that had less focus on Extreme Programming.

Even after about 15 years, I believe this book still is an important cornerstone in defining what users stories are and how you should approach them in every part of their lifecycle. The book gives tons of practical advice on how to work with user stories. Therefore, I think it's a must-read when you're new to User Stories.

Once you've had a proper training on user stories and have been using them for a few months, the majority of the book just makes sense and is pretty basic. In a non-digital world, I would grab back to the book from time to time to adjust my way of work. In a digital world, Mike's blog is available for most of those pushes into the right direction: https://www.mountaingoatsoftware.com/...

I just did a refresher on this book and realised there is a lot of stuff there which is very relevant. It is a must-read for everyone working with user stories and agile delivery.

Very good book

This is an essential lecture book for all professionals that wants to get a better understanding of user stories and how to apply it. I think that today is a classical book in the library of everyone dedicated to agile.

This is not exactly the book to LEARN how to make user stories, but rather how to apply them to your project. Exactly as the title describes. However, you do not have to be an expert in creating user stories to find this very useful. Also, enough details about SCRUM are described that you could find this book a great overview.

Found this immensely useful and took a great many notes.