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
tags: change_management, change_management, change_management, change_management contains: gd_guidl__change_change_request, gd_temp__change_feature_request, gd_temp__change_component_request, gd_temp__change_impact_analysis, gd_temp__component_classification, gd_temp__change_decision_record has: doc_concept__change_process, doc_getstrt__change_process needs input: wp__policies, wp__issue_track_system, wp__feat_request, wp__cmpt_request outputs: wp__issue_track_system, wp__feat_request, wp__cmpt_request responsible: rl__contributor approved by: rl__architecture_community supported by: rl__platform_team satisfied by: gd_req__change_attr_uid, gd_req__change_attr_status, gd_req__change_attr_title, gd_req__change_attr_impact_description, gd_req__change_attr_impact_safety, gd_req__change_attr_impact_security, gd_req__change_attr_types, gd_req__change_attr_affected_wp, gd_req__change_attr_milestone, gd_req__change_attr_mandatory, gd_req__change_tool_impact_analysis
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”
wf__change_create_cr		Workflow

Analyze Change Request		status: valid
tags: change_management, change_management, change_management, change_management contains: gd_guidl__change_change_request, gd_temp__change_feature_request, gd_temp__change_component_request, gd_temp__change_impact_analysis, gd_temp__component_classification, gd_temp__change_decision_record has: doc_concept__change_process, doc_getstrt__change_process needs input: wp__policies, wp__issue_track_system, wp__feat_request, wp__cmpt_request outputs: wp__issue_track_system, wp__feat_request, wp__cmpt_request responsible: rl__architecture_community approved by: rl__project_lead supported by: rl__platform_team satisfied by: gd_req__change_attr_uid, gd_req__change_attr_status, gd_req__change_attr_title, gd_req__change_attr_impact_description, gd_req__change_attr_impact_safety, gd_req__change_attr_impact_security, gd_req__change_attr_types, gd_req__change_attr_affected_wp, gd_req__change_attr_milestone, gd_req__change_attr_mandatory, gd_req__change_tool_impact_analysis
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.
wf__change_analyze_cr		Workflow

Implement and Monitor Change Request		status: valid
tags: change_management, change_management, change_management, change_management contains: gd_guidl__change_change_request, gd_temp__change_feature_request, gd_temp__change_component_request, gd_temp__change_impact_analysis, gd_temp__component_classification, gd_temp__change_decision_record has: doc_concept__change_process, doc_getstrt__change_process needs input: wp__issue_track_system, wp__feat_request, wp__cmpt_request outputs: wp__issue_track_system, wp__feat_request, wp__cmpt_request responsible: rl__delivery_team, rl__platform_team approved by: rl__delivery_team, rl__platform_team supported by: rl__project_lead satisfied by: gd_req__change_attr_uid, gd_req__change_attr_status, gd_req__change_attr_title, gd_req__change_attr_impact_description, gd_req__change_attr_impact_safety, gd_req__change_attr_impact_security, gd_req__change_attr_types, gd_req__change_attr_affected_wp, gd_req__change_attr_milestone, gd_req__change_attr_mandatory, gd_req__change_tool_impact_analysis
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. Depending on the type of the Change Request (Feature or Component), different Teams are responsibly for this workflow. For feature: Before closing the Change Request, Platform Team must check the correctness. For component: Before closing the Change Request, Delivery Team must check the correctness. The responsible team may still reject it, thus the status is set to “rejected”.
wf__change_implement_monitor_cr		Workflow

Close Change Request		status: valid
tags: change_management, change_management, change_management, change_management contains: gd_guidl__change_change_request, gd_temp__change_feature_request, gd_temp__change_component_request, gd_temp__change_impact_analysis, gd_temp__component_classification, gd_temp__change_decision_record has: doc_concept__change_process, doc_getstrt__change_process needs input: wp__issue_track_system, wp__feat_request, wp__cmpt_request outputs: wp__issue_track_system, wp__feat_request, wp__cmpt_request responsible: rl__delivery_team, rl__platform_team approved by: rl__delivery_team, rl__platform_team supported by: rl__project_lead satisfied by: gd_req__change_attr_uid, gd_req__change_attr_status, gd_req__change_attr_title, gd_req__change_attr_impact_description, gd_req__change_attr_impact_safety, gd_req__change_attr_impact_security, gd_req__change_attr_types, gd_req__change_attr_affected_wp, gd_req__change_attr_milestone, gd_req__change_attr_mandatory, gd_req__change_tool_impact_analysis
The Change Request is closed. Depending on the type of the Change Request (Feature or Component), different Teams are responsibly for this workflow. For feature: The Change Request is closed only, if the implementation is sufficient. That is verified by the Platform Team finally, especially the selected codeowners of the team must approve. For component: 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 responsible teams keeps the status “in implementation”.
wf__change_close_cr		Workflow

RAS(IC) for Change Management:

RASIC Overview for Change Management

Activity	Responsible	Approver	Supporter
wf__change_create_cr	rl__contributor	rl__architecture_community	rl__platform_team
wf__change_analyze_cr	rl__architecture_community	rl__project_lead	rl__platform_team
wf__change_implement_monitor_cr	rl__delivery_team; rl__platform_team	rl__delivery_team; rl__platform_team	rl__project_lead
wf__change_close_cr	rl__delivery_team; rl__platform_team	rl__delivery_team; rl__platform_team	rl__project_lead