Change

What is Change?

In project management, change refers to any modification, addition, or removal that affects a project’s scope, timeline, cost, and/or quality. It may arise from external factors like market shifts, stakeholder input, or internal factors such as new technology or revised business goals. While some changes can improve project outcomes, unmanaged changes often disrupt schedules, increase costs, or lower quality. Effective change handling requires structured processes and clear communication to maintain control and alignment with project objectives.

Key Points

• It can be planned (proactive) or unplanned (reactive), depending on how and when it is introduced into the project lifecycle.
• It affects one or more triple constraints: scope, time, and cost.
• Change management frameworks help assess, approve, and implement changes in a controlled manner.
• Stakeholder communication is vital for understanding the need for change and ensuring alignment.
• Uncontrolled or frequent changes can result in scope creep, leading to project failure.

Related Terms

• Change control is the formal process used to evaluate and decide whether proposed modifications should be approved or rejected.
• Scope creep occurs when modifications are introduced without proper documentation or control, expanding the project beyond its original objectives.
• Project governance defines who can authorize changes and how decisions about them are communicated and enforced.
• Stakeholder management involves keeping all parties informed and engaged during the assessment process.
• Risk management helps identify and mitigate the potential adverse effects of a proposed modification on project outcomes.

Change: Example

A software development team is building an application for a client. Halfway through the project, the client requests a new feature that was not part of the original plan. The project manager initiates a request, assesses its impact on time and budget, and presents it to the project board for approval. Once approved, the team adjusts the schedule and scope to include the new feature.

Change: Best Practices

• Use a structured control process to evaluate every request.
• Communicate the implications of proposed modifications to all stakeholders before making decisions.
• Document all alterations thoroughly, including their rationale, expected impact, and final decision.
• Align requests with project goals and strategic objectives to ensure they add value.
• Limit modifications during later stages of the project unless necessary to reduce risks and delays.

Additional Resources

Preparing for a PMI certification?

• Exam Prep Courses: PMP^®, CAPM^®, and PMI-ACP^®
• Exam Simulators: PMP^®, CAPM^®, PMI-ACP^®, PMI-PBA^®, PMI-RMP^®, PMI-SP^®, PgMP^®, and PfMP^®
• Professional Development Units (PDUs): 15, 30, and 60 PDU Bundles