A user story must be associated with the same product, release, and sprint as the requirement. Once the user story is created, to complete full information about the user story, edit the user story details.
To create a user story
The Requirement Details 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". Follow your organization's convention.
Defines the number of points estimated to complete the user story. Point values must be expressed as integers. Decimals are not allowed.
Specifies the user story's current status.
Values
Default: Planned
Specifies the user story's importance in the product.
Values:
Default: Medium
Defines the purpose of the user story and provides additional relevant information.
Specifies the name of the product with which the user story is associated.
Specifies the release with which the user story is associated.
Specifies the sprint in which the user story is completed.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |