All About Agile | Agile Development Made Easy

Lifecycle of a User Story

by Mark Levison, 4 November 2013 | The Agile Blogosphere

This post is from Agile Pain Relief by Mark Levison. Click here to see the original post in full.

Life Cycle from: Stories are often used as a lightweight form of Agile requirement. Their goal is  to replace heavy weight-specification documents with “a Card, a Conversation and a Confirmation”. When people first discover User Stories it’s hard to see how they work because we often take a static viewpoint – i.e. we only see them at Release Planning or during implementation. We’re left with many questions: Where do User Stories come from? When are they created? Who is involved in their creation?

To illustrate this I will use vignettes from the WorldsSmallestOnlineBookStore. Each vignette will show what happened to one User Story.

 “As a frequent book buyer I want to save my address so that I don’t have to retype it every time I visit the bookstore”

During the team’s first Release Planning Session (aka Initial Product Backlog Refinement) this Story was identified. After a few rounds of planning poker the consensus estimate was that it was size 20, allowing for both the initial entry of the address, updating...

read more


Leave a Reply

What is 6 + 5 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)