DESCRIPTION
The aim of these 2 documents is to capture all change requests made to a project in terms of scope, time and / or budget. Each change request should be formally documented and approved /rejected.
A project change control process is defined in the Project Control section of the P03 – Project Management Plan and should form part of the following phases in the p3mg PM Framework project lifecycle: Plan, Build & Test, Deploy & Handover
The Project Change Request Form is utilised as a tool to capture, evaluate, and approve or reject all changes that will affect the agreed project baseline. Only fully documented change requests should be accepted, reviewed for impact, and then implemented when approved.
The Project Change Register should list all requested change requests (both accepted and rejected). The Register provides a list of project variance items that can then form part of Project Progress Reports or Post Implementation Reviews. One register should exist per project.
These documents are part of the p3mg PM Framework
Got a question about the product? Email us at support@flevy.com or ask the author directly by using the "Ask the Author a Question" form. If you cannot view the preview above this document description, go here to view the large preview instead.
Source: PC02 - Project Change Request Form & Change Register Word (DOCX) Document, p3mg Consulting
Project Scope Work Breakdown Structure Business Case Example Project Kick-off
Download our FREE Strategy & Transformation Framework Templates
Download our free compilation of 50+ Strategy & Transformation slides and templates. Frameworks include McKinsey 7-S Strategy Model, Balanced Scorecard, Disruptive Innovation, BCG Experience Curve, and many more. |