Overview A user story is a very high-level definition of a requirement that provides just enough information that the developers can provide a reasonable estimate of the effort to implement the requirement. They are written in such a way as to guide and direct the design and development activities, are a vibrant collection of text which captures the spirit of the way that a user will interact with the system.

Key Terms

User Story: A brief simple description of a feature from the perspective of the person desiring the feature and structure is often something like this: "As a [user], I want [goal] so that [reason]."Acceptance Criteria: The criteria that must be met by the user story to be considered fulfilled and successful.Backlog: The prioritized list of user stories that at any time is ready to be picked up by the Development Team on which they can start work.Description:

Identify Users and Goals: Understand who the users are and what it is they actually want to do. This should help in brainstorming relevant and meaningful user stories.

User Story: INVEST in writing user stories in a typical standard format, which is short and simple. It should relate to only one objective-a certain value to the user.

Acceptance Criteria: These are what should hold true for the user story to be complete; basically, how the development team can check if the needs of the user have been met.

Backlog Prioritization: Ranking based on the level of importance and estimated value that the stories will have for users. Tackle first the uphill jobs.

Sharing User Stories with Teams: Share the user story across design and development teams so that the goals of the user and how the product will help the user can be understood across teams.

Iteration Based on Feedback: You will constantly iterate user stories based on the feedbacks given by users and stakeholders to accurately capture the needs and goals of users' ever-evolving goals.
‍

For Further Reading:

"User Story Mapping" by Jeff Patton: A book on how to create shared understanding of user needs using user

Example: Suppose you are developing a mobile banking application. Thus, the user story would go this way: "As a user, I would want to be able to transfer money fast and conveniently so that I can pay my bills on time." This tells the direction on how to build an easy, convenient feature of money transfer.

Trello: You can do the organization and prioritization of your user story with your full team together; this tool visualizes it. See Trello.