What are user stories?
Within Agile Development user stories describe features of a system from a front end user perspective.
Why use user stories?
User stories are extremely helpful for both a client and a developer. They allow a client to get a feel for how a system will work and specify exact features before development starts. For a developer they act as a great guide to building aspects of the system to ensure the system or feature meets the clients expectations.
When should user stories be written?
User stories are usually intially developed at close to the start of a project. This ensures that everyone knows what to expects from a system. However the are evolved as the project goes on, to allow for new feature or user roles.
How to write a user story
- Define user types in the system (e.g. End User, Editor, Admin)
- Break the system or new feature into small chunks, usually into pages within a system
- Decide on the types of users that can access this page/feature
- Break the page/feature down into smaller parts (e.g. I can see my profile picture, I can see a menu)
- Specify the location of the feature/page
Example User Story
- Feature - User Profile Page
- Location - Front end - profile
- User type - Front end users
- Story :
- I can see me profile picture
- I can change my profile picture
- I can see my latest notifications
- I can see my most recent visited items
- I can see a menu to navigate to other pages
- I can see my recent messages
User stories can take different forms and do not have to work to a specific template, they just need to be presented in a way that is understandaable to all parties.