Why is change documentation needed for a project Why cant th

Why is change documentation needed for a project? •Why can\'t the project manager just provide verbally directed changes? •What are the consequences to project control if changes are not handled in a formally documented process?

Solution

Hi,

Below is the solution to your question:

Why is change documentation needed for a project?

Projects are suspectable to changes right from the initiation and planning process. When the changes are chronologically entered it becomes easy to followup on information and be able to also gather information sequentally. A change document provides clarity and transperency to the process of change. It provides clear connection between the change proposal and the end result. It provides the project managers, sponcers, streeing commitee members and all the other stake holders with the standerd process of managing changes on the project.

Change management docomentation helps to manage change requests so that approved changes will be controlled, ensuring the project remains on schedule, within the budget etc.

The main purpose of change management documentation is

Why can\'t the project manager just provide verbally directed changes?

The project manager cant always provide verbally directed changes because

What are the consequences to project control if changes are not handled in a formally documented process?