|
Step
|
Tool guidance
|
|
1 Place non-urgent requests on the Program Roadmap
Requests that are determined to non-urgent (low Cost of Delay) are deferred for future
release planning in the Program Roadmap.
|
<Tool-specific steps / online help>
|
|
2 Assign urgent requests to the current release
Requests that are urgent to consider for the current release (high Cost of Delay) are reviewed by the
Program Manager and the Program Release Manager.
|
<Tool-specific steps / online help>
|
|
2.1 Create features for urgent requests
The Program Manager creates a new Feature.
|
<Tool-specific steps / online help>
|
|
2.2 Associate each new urgent feature to an appropriate Epic
|
<Tool-specific steps / online help>
|
|
2.3 Assign each new urgent feature to the current release
|
<Tool-specific steps / online help>
|
|
2.4 Follow-up
The assignment of a new Feature to the current release results in a notification to the
Enterprise Architect, who assigns size requests to the appropriate execution teams. The
Program Release Manager negotiates a new committed release plan with the execution teams.
|
<Tool-specific steps / online help>
|
