Writing User Stories
In agile teams, requirements are often documented in the form of user stories. A user story is a concise, informal description of a user need or feature, written from the end user's perspective ("As a [type of user], I want [function] so that [value/goal]").
The purpose of this is to make clear to everyone what value a function delivers for the customer/user. By documenting requirements in this way, the team remains focused on the user and the why behind each feature. Moreover, user stories form the basis for work planning (the product backlog) and establishing acceptance criteria.
Starting Points
Key Points
- Requirements are formulated as user stories instead of loose requirements. Each user story indicates who wants something, what they want, and why.
- Each story contains criteria or conditions that indicate when the functionality is satisfactory (acceptance criteria).
- The backlog with user stories is maintained and up-to-date. You actively think about prioritizing and splitting stories, and adjust stories when insights change during the project.