|
|
|
Sometimes a user story requires the delivery of the feature for another user story or its functionality before it can be implemented. For example, a user story that provides access to online help depends on completion of user story for a Help button in the user interface. You can create dependencies in the user story detail to note these requirements. The dependency must be a user story in the same product.
When you create a user story dependency, the detail for the dependent story also updates the section Dependencies on this user story. Team members can view the dependency details, the date the feature must be delivered, the team, assignee, and the status of the user story. Clicking the dependent user story title opens the User Story Detail page for the dependent user story.
To create a dependency on a user story
The Story Dependency Edit page appears.
Defines the required feature or functionality required by the current user story.
Required: Yes
Limits: 255 characters
Specifies the title of the user story on which this user story depends. Enter a few characters of the user story title to display a list of suggestions.
Defines the reason for the dependency, and other pertinent information about the dependency.
Specifies the date when the dependent feature or functionality must be delivered. If the dependent user story is assigned to a sprint, then due date must be the first day of that sprint.
Required: Yes
Limits: 255 characters
Specifies the title of the dependent user story. This field is automatically populated with the title of the current user story and cannot be changed.
The story detail updates to reflect the dependency details.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |