Change Control Process Description [Describe the CCP process, including the roles and responsibilities, inputs and outputs, and how it identifies, manages, and tracks CRs through implementation. Include a swim lane diagram.] Change Control Board [Document membership for the project’s CCB. A typical CCB includes the product manager, development manager, Project Manager, test lead or manager, subject matter experts, business analysts, senior management, and clients, if warranted. The CCB should remain relatively small and have the breadth of expertise and ability needed to respond to requests promptly and efficiently.] Project Change Request Tracking [Describe what type of tracking mechanism the project will use to track the status and implementation of CRs. Depending on the size and complexity of a project, this may include an automated tool or a more simplified tool such as a spreadsheet.] Change Request Reporting [Describe the CR reporting needs on the project, including the title, frequency, content, and usage.] Example: Title Frequency Content Usage Opened, Pending, Regularly Summary of the CRs that have been Keeps the project and Approved CRs Scheduled opened, still pending and approved since team and Team the last reporting. Stakeholders Meeting informed about (Weekly) the changes being made. CR As Completed Lists all CRs approved for implementation, Used by Implementation activities to implement, estimated management, Status completion date, and current status. the CRC, and CR Owners to track CR implementation. Metrics Report Monthly Identifies the total number of CRs opened, Include as part of approved and pending. Include aging quality reporting. statistics that show how long it takes to approve a CR, the duration at each phase of the process, the number of CRs referred to CCB and ESC, and the number of rejected CRs.
Change Control Process Description [Describe the CCP process, including the roles and responsibilities, inputs and outputs, and how it identifies, manages, and tracks CRs through implementation. Include a swim lane diagram.] Change Control Board [Document membership for the project’s CCB. A typical CCB includes the product manager, development manager, Project Manager, test lead or manager, subject matter experts, business analysts, senior management, and clients, if warranted. The CCB should remain relatively small and have the breadth of expertise and ability needed to respond to requests promptly and efficiently.] Project Change Request Tracking [Describe what type of tracking mechanism the project will use to track the status and implementation of CRs. Depending on the size and complexity of a project, this may include an automated tool or a more simplified tool such as a spreadsheet.] Change Request Reporting [Describe the CR reporting needs on the project, including the title, frequency, content, and usage.] Example: Title Frequency Content Usage Opened, Pending, and Approved CRs Regularly Scheduled Team Meeting (Weekly) Summary of the CRs that have been opened, still pending and approved since the last reporting. Keeps the project team and Stakeholders informed about the changes being made. CR Implementation Status As Completed Lists all CRs approved for implementation, activities to implement, estimated completion date, and current status. Used by management, the CRC, and CR Owners to track CR implementation. Metrics Report Monthly Identifies the total number of CRs opened, approved and pending. Include aging statistics that show how long it takes to approve a CR, the duration at each phase of the process, the number of CRs referred to CCB and ESC, and the number of rejected CRs. Include as part of quality reporting.
Change_Control_Management_Plan_Template_with_Instructions.docx