Change Management Workflows#
For a detailed explanation of workflows and their role within the process model, please refer to the Introduction.
Create Change Request
|
status: valid
|
||||
The Change Request is created. For creating the Change Request template must be used. Check here for the available templates: Getting Started on Change M... or Change Request Guideline. To start the analysis the Change Request status is changed to “in review” |
|||||
Analyze Change Request
|
status: valid
|
||||
The Change Request is analyzed. Until the template is not filled out properly, the Change Request may be set back to “open” from the Architecture Team. If the Change Request shall be implemented, the Change Request status is set to “in implementation”, otherwise to “rejected”. If the author, Contributor. of the Change Request decides to cancel it, thus the status is set to “rejected” too. |
|||||
Implement and Monitor Change Request
|
status: valid
|
||||
The Change Request is implemented and monitored. This may require additional activities, including creating ISSUEs and PRs. These are linked to the Change Request and monitored until closure. The Change Request is done, if all linked activities has been closed and confirmed, which is done by the approval of the selected codeowners. Before closing the Change Request, Delivery Team must check the correctness. The Delivery Team may still reject it, thus the status is set to “rejected”. |
|||||
Close Change Request
|
status: valid
|
||||
The Change Request is closed. The Change Request is closed only, if the implementation is sufficient. That is verified by the Delivery Team finally, especially the selected codeowners of the team must approve. Otherwise the Delivery Team keeps the status “in implementation”. |
|||||
RAS(IC) for Change Management:#
Activity |
Responsible |
Approver |
Supporter |
|---|---|---|---|