User story is a popular method in agile software development to capture the need of user of a function or feature that are being developed. A User story consist of couple of sentence that describes “Who”, “What” and “Why”.

In the requirements process User Storys can be used as a method to define business value that needs to be created. Often and preferably the User story should be handwritten on a paper or post-it to make sure you can’t write too many details.

Usually the stories are written by the customer or the business user to influence the functionality and make sure to answer “Who”, “What” and “Why”.

When it’s time to write a User Story, make sure to gather the right team and don’t do it by youself. At least one from the development team should participate to ensure that the stories capture as much as possible.

User storys can preferably be used as a acceptance criteria or/and acceptance test case before the task is done “shippable”.

Read more:

Thanks to Jimmy Janlén for letting me use his pictures from Agile Topics Cards.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s