Change

Change Management

Changes in the scope of projects are usually inevitable and they impact especially on the time and scope of the project. Changes in the scope of the Cricket and raffle event s should be rigidly controlled and this requires a change control procedure. This section outlines the process to monitor and control changes in the project.

a. Change Management Process

Change Management will be implemented using a Change Management Process that documents and implements requests for change will follow a stepwise process as indicated by Turner (2009, 294) with some modifications.

Step 1: Identify Need for Change: Changes deviating from the project plan has to be identified for appropriate action to be taken. Changes originating from the charity, the client, the University, Heath and safety, the project team or participating teams will be considered. The required changes may be as a result of a change in requirements, an improvement to one or more project deliverables, an indication that a deliverable will no longer meet the project requirements or as a result of the identification of a new risk requiring a change to a project deliverable or the introduction of a new deliverable.

Step 2: Request and Log of Change: A formal request for change has to communicate to the project team immediately the need for changes arises. A project team member identifying the need for the change will request the need for change by logging the change on the Change Control Form as shown in the Table 1. The request will include the name of the project team member, the signature, date of the request, project, milestones, activity and a clearly defined description of the proposed change. Project change that has been requested and logged will have been checked by other members of the project team. Members checking the change request will include their names, signatures and date the checking has taken place.

Step 3: Assessment of the impact of change: The...