*

What is a User Story?

User Story Lifecycle Phase I

User Story Lifecycle Phase II

User Story Lifecycle Phase III

*

• An agile expression

of a requirement

focusing on valueAs a <role>

I want <action>

So that <business value>

• Provides structure

• Promote discussion and collaboration

• Light-weight approach using simple

language understood by all participants

in a project <role> : actor performing the action

<action> : what will happen (not how)

<business value> : what upon completion

this user story contributes to the overall

goal

*

Story Lifecycle I - Creation ->

Ready for Estimation

• An idea comes from Stakeholders in the form of :• Change request

• New functionality

• A Product Owner captures a business request and

creates a user story

• The user story is added to the backlog

• The user story is groomed by the Product Owner

with assistance from the Sprint Team

• The user story is broken down and acceptance

criteria is created through discussion

• Prioritization is started

• The user story is now ready for sizing

Backlog Grooming• Breakdown

• Acceptance criteria

• Sprint team

contributions

Idea

Idea is

captured and

a story is

created

*

Estimation• Acceptance criteria

• Sprint team

contributions

• Story point assignment

Story Lifecycle II – Sizing (Agile Estimation)

• The user story is groomed and right sized for an iteration

• The sprint team sizes each story on the list, using relative sizing called a

Story Point

• A story point (size) is assigned to the user story through triangulation to like

stories

• The user story is available for more precise prioritization into sprints

• The user story is ready for sprinting (can be accepted by the team into a

sprint iteration)

*

Story Lifecycle III – During the sprint iteration• The user story is accepted into the sprint iteration by the sprint team during planning

• The sprint team decides the various tasks to meet the acceptance criteria specified

• The sprint team completes the tasks required to meet the definition of done for tasks and

stories

• The user story is demonstrated at the end of the sprint iteration to the Product Owner during

the review

• The Product Owner accepts or rejects the story based on if it meets the acceptance criteria

• The user story is considered complete and closed or dropped and returned to the backlog for a

future iteration

Tasks are completed

Sprint iteration

Returned to backlog to be reprioritized

Returned to backlog and closed

* For more Agile information please

visit our websites

* www.torak.com

* www.agiletestingframework.com

*