You don't write user stories: you tell them! O.K., maybe writing them is optional. But the main element is the conversation, along with the confirmation. The card is optional. And User Stories front-end your Scrum process: while they are a potentially useful approach for the team to socialize possibilities with end users, you won't find one on a Product Backlog!
User Stories are the most popular requirement technique in Agile software development. A User Story describes a requirement as a piece of functionality that a user needs, and the description is not longer than it can easily be written in hand on an index card (Story Card).
The strength of User Stories is that it is easy to get started, and they are a good starting point for further investigation. User Stories also work well as Product Backlog Items that can be ordered and estimated.
The traditional requirement management challenges related to accuracy, detail level, dependencies, traceability, and testability have not gone away with User Stories. While user stories cannot completely address the requirements problem, they go a long way to help Agile development projects bring the business and development together in conversation. It also helps the requirement effort get off to a lightweight, high-velocity start.
In this course we will write User Stories and we will explore the benefits and the limitations of User Stories.
Warm-up Narratives
Brainstorm Features
User Role Modeling
Writing the User Stories
Include User Motivation
Constraint User Stories
Organize the User Stories
Supplemental Information
User Stories and behavior
User Stories and test