Typically, a panel of key stakeholders reviews the requirements for an upcoming release. The stakeholders analyze the requirements and rank them after discussing the priorities. The rankings are edited and the overall priority is calculated immediately. The ability to see the candidate requirements and edit the ratings for each requirement for each stakeholder is important to assess a requirement business impact.
You can define the requirement business priorities using the Requirement: Properties - Business Priority page. Assess the priority and graphically represent the overall business priority on the Requirements page.
Follow these steps:
The general page appears.
Displays the overall requirement priority based on a weighted average formula based on rankings for the various priorities.
Defines the requirement business priority for innovation and user experience.
Values:
Default: Unassigned
Defines the requirement business priority for revenue impact.
Values:
Default: Unassigned
Defines the requirement business priority for developer productivity.
Values:
Default: Unassigned
Defines the requirement business priority for cost of operations and support.
Values:
Default: Unassigned
Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |