2010 08 Jul
I searched the internet about the best ways to represent the use cases and the user stories in agile project, I faced many points of views that fit all in the same basic standard format:
As an <actor> I want to <action> so that <achievement>
This way of representing a user story is indicative and helps explaining the needed requirements to team members, but in big systems where the number of user stories is huge I see that the above representation becomes complex and less indexable and hard to manage, so I did more researches and consultancy work what lead me to refine the representation to a more indexable way to create the product backlog.
|
As an <actor> I want to <action> so that <achievement> |
I am using Microsoft word when I am writing my user stories and I sort the stories by actors.
User Stories
Map Module
|
Actors |
Administrator: the person that is responsible of adding the data to the map Visitor: a person generating the report |
As An Administrator
|
User story Id |
I want to |
So that |
|
1 |
Add new data to the map |
So visitors can generate reports |
|
2 |
Edit existing data on the map |
So visitors can generate reports |
As A Visitor
|
User story Id |
I want to |
So that |
|
3 |
Generate reports from the map |
So that I can see the population chart |
I find this template very effective when writing the stories and easy to read and index. It’s easy to find the stories by using the table of content of MS Word.
Great! but i think we need more details to be able to replace the use cases by user stories !
just u need to draw the uml use cases in order to help you in writing test cases, but in the description i don't feel like you need more! what do u think ?