Main Description |
The user story work item contains the user story description and details that help the team implement and validate the
user story implementation.
State
|
Definition
|
Following Action
|
Following State
|
Task/Activity
|
|
|
Identify
|
Identified
|
Plan Iteration
|
Identified
|
Newly identified or reopened story (which has not been detailed
yet)
|
Defer
|
Deferred
|
Plan Project
|
Start Working
|
In Progress
|
Develop User Story
|
In Progress
|
Story is assigned to a team member and is being detailed and
developed
|
Defer
|
Deferred
|
Plan Project
|
Mark Implemented
|
Implemented
|
Develop User Story
|
Reopen
|
Identified
|
Manage Iteration
|
Implemented
|
Story has been implemented and unit tested, but not tested for acceptance
yet
|
Defer
|
Deferred
|
Plan Project
|
Reopen
|
Identified
|
Plan Iteration
|
Reiterate
|
In Progress
|
Develop User Story
|
Mark Done
|
Done
|
Test
|
Done
|
Story has been successfully tested for acceptance
|
Reopen
|
Identified
|
Plan Iteration
|
Deferred
|
Story is deferred or removed from the backlog, for one of the
reasons:
-
Duplicate
-
Implemented
-
Implemented Upstream
-
Later
-
Won't Implement
-
Works For Me
|
Reopen
|
Identified
|
Plan Iteration
|
Table 1 - State machine of the user story work item
There are different approaches for the creation of user stories. The analyst could create the user story work item in
IBM Rational Team Concert while the high level requirement that originated
the user story is being detailed in a requirements management tool. Alternatively, the analyst or team lead could
create and detail the user story work item in Rational Team Concert during iteration planning. In both cases the user
story work item instances do not represent the story or the work performed to implement the story, but rather only
properties and status of the story. To explicitly represent, manage, and track the concrete work to be done to realize
a story, the story is refined with development tasks as recommended by Develop User Story activity.
|