You can create a user story to describe work items for a sprint. Create the user story from the Planning Backlog page.
Follow these steps:
The User Story Edit page appears.
Specifies the name of the user story.
Required: Yes
Limits: 255 characters
Example: Many Agile teams use the format: "As a ___ I want to ___ so that ___". For example, "As a user, I want to see home page when I log in so that I can view my current tasks".
Specifies the status of the user story.
Values:
Specifies the importance of the user story in the product.
Values:
Default: Medium
Defines the number of points estimated to complete the user story. Point values must be expressed as integers. Decimals are not allowed.
Specifies the team member who owns the user story.
Note: You can assign the user story to a Agile Vision user who is not a member of the scrum team that owns the story.
Example: A member of another team assists with code review.
Defines this user story as the child of an existing epic. You can move a user story from one epic to another from the edit page of the user story.
Defines the purpose of the user story and provides additional relevant information.
Specifies the unique name of the product.
Specifies the release to associate the user story with.
Specifies the sprint in which the user story is completed.
Specifies the themes that the user story is part of. The user story is listed on detail pages of all the selected themes.
Specifies the scrum team assigned to complete the user story. The list of available teams is limited to the teams assigned to the sprint.
Default: None
Defines the master release with which the user story is associated. You can assign the user story to a master release only if the product is associated to a master release. If the product release is associated with a master release, the user story is automatically assigned to the same master release.
If you select a product release that is associated with a master release, the master release field in the user story is overwritten. If the user story was originally assigned to a different master release, it is now assigned to the same master release as the product release.
The User Story Detail page appears. From this page you can view and manage all information relating to the story, and create tasks as sub-items of it.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |