CASECHANGE CONTROL MANAGEMENT PROCESS OVERVIEW: A change control management process is a method that formally defines, evaluates, and approves application changes prior to their implementation into live or production environments. The process includes several control procedures to ensure that implemented changes will cause minimal impact to the objectives of the organization. These procedures involve submission of change requests, determination of feasibility, approval, and implementation. The following describes typical roles and procedures undertaken in a change control management process. ROLE: CHANGE REQUESTER The Change Requester identifies a requirement for change to the application (e.g., upgrades to new editions, etc.). The Requester then prepares a Change Request Form (CRF), including description of the change, cost and benefits analyses, impact, approvals, and any other supporting documentation deemed necessary. He or she then submits the CRF to the Project Manager for further review. ROLE: PROJECT MANAGER Upon receipt, the Project Manager reviews the CRF and determines whether or not additional information is required for the Change Control Board to assess the full impact of the change in terms of time, scope, and cost (i.e., feasibility). The decision is based among others on factors, such as: 0 Number of change options presented 0 Feasibility and benefits of the change - Risks and impact to the organization 0 Complexity and/or difficulty of the change options requested - Scale of the change solutions proposed If the Project Manager determines the change is feasible, he/she will log the CRF in the change log by number, and track its status. The Project Manager then submits the CRF to the Change Control Board. On the other hand, if the CRF is not deemed feasible, the Project Manager will close the CRF. ROLE: CHANGE CONTROL BOARD Upon receipt, the Change Control Board reviews the CRF and any supporting documentation provided by the Project Manager. The Change Control Board represents an authorized body who is ultimately responsible for approving or rejecting CRFs based on relevant analyses (i.e., feasibility). After a formal review, the Change Control Board may: 0 Reject the change (the reasons for the rejection are notified back to the Change Requester) 0 Request more information related to the change 0 Approve the change as requested or subject to specified conditions Once approved, the Change Control Board forwards the change and any related supporting documentation to the Implementation Team. ROLE: IMPLEMENTATION TEAM The Implementation Team schedules and tests the approved change. If test results are not successful, the change and all related supporting documentation are sent back for retesting. If results are successful, the Implementation Team formally implements the change, and notifies the Change Requester. PROJECT TASK: Prepare a flowchart depicting the change control management process just described. Make sure you segregate the roles (i.e., Change Requester, Project Manager, Change Control Board, and Implementation Team) in vertical columns when creating the flowchart to illustrate the procedures performed in the process. This representation is useful for auditors to evaluate segregation of duties and identify incompatible functions within the process