84 - Change Request
Outputs of Planning Processes
- The most common output across various processes in monitoring and control is Change Requests.
- Change requests are vital for modifying the project plan after execution has begun.
Planning Processes Overview
- There are 24 planning processes.
- The output of these processes culminates in the Project Management Plan.
- Once execution starts, the project management plan should not be changed unless through an approved change request.
Need for Change Requests
- Changes may be required at various stages due to factors such as:
- Changes in budget estimates (e.g., discovering more funds are needed).
- Changes in project scope (e.g., customer requests to add or remove features).
- Change Request: A specific proposal to change components of project documents, deliverables, or baselines.
Types of Changes Addressed by Change Requests
- Change requests can modify various project elements, which may include:
- Adjusting project scope (add/remove work).
- Changing timelines (extend or shorten project duration).
- Altering costs (make a project more cost-effective).
- It's important to note that change requests aren’t only initiated by customers.
Initiating Change Requests
- Project managers may need to issue change requests due to:
- Issues arising during project execution which need corrective or preventive actions.
Corrective Actions
- Taken when a project is found to be off track:
- Example: If a project is behind schedule or over budget, a manager might seek additional time or funds.
Preventive Actions
- Proactive measures aimed to keep the project on track:
- Example: Anticipating an issue that might delay progress and requesting adjustments before it happens.
Defect Repair
- Refers to repairing broken components within the project:
- Common in IT projects where various failures may occur, requiring systematic fixes.
Conclusion on Change Requests
- Change requests are integral for adapting the project management plan based on evolving needs.
- It’s critical to remember that a change request does not guarantee approval; it must first be assessed and authorized before implementation.