尚德科技Change Management Procedure.DOCVIP

Change Management Procedure Change management controls any additions, deletions, or modifications to the scope and the project plan; including changes to the to-be flows. The type of change to the project affects the scope documents. The investigation of a proposed change evaluates its effect on budget dollars, schedule, and resources. Not all aspects of a project can be determined in advance. Change from internal or external sources to the scope and project plan need to be accommodated through the life of the project. All requests for changes must be evaluated and approved (or disapproved) in order to recognize and control scope creep. The project manager should establish a formal procedure for introducing changes into the project’s plan, goals, and objectives, whether or not they affect the scope of the project. Use a change request form that can record submissions, investigation, review, and approval. All requests should be recorded on a change request log where their status can be tracked. The project administrator is responsible for maintaining the log by recording new change requests, updating change requests, and identifying status of change requests.  Change Request Approval/Acceptance Procedure The life cycle of a change request follows a defined procedure, summarized by the phrase: ID, Estimate, and Approve. 1. A team member identifies a need for a change. 2. The member fills out the change request form, first describing the proposed change and then enumerating the reasons for it. 3. The project manager (and senior management) analyzes the request. 4. If the manager (and senior management) gives preliminary approval, the request is investigated by an assigned party. 5. Management considers the effect of the change, specifically how it will affect the scope of the project and budget. 6. Following the investigation, management convenes and evaluates the change request and the results of the investigation. 7. Management designates the change request a