How to Create a Project Change Management Process

Request — Request a change to the project, if warranted.

Review — Review the impact of the proposed change.

  • Description of proposed change and reason the change is needed. (This should have been captured in the request.)
  • Proposed changes to scope inclusions and exclusions. (You should confirm your understanding of this with the client.)
  • Anticipated change in complexity (In this case, I am using the term complexity in a generic way to refer to whatever estimation method you are currently using, whether you use actual durations, story points, ideal days, or some other defined units.
  • Anticipated impact on the finish date. (Consider any impact on the team, given other workloads, vacation schedules, etc.)
  • Anticipated impact on budget. (Consider that there may be some changes that actually reduce costs or eliminate scope.)
  • Any impact on risks. (At this point, at a minimum, new risks should be defined, documented, and discussed.)

Resolve — Resolve whether the proposed change should be approved or not.

Revise — Revise the project plan.

  • Break down project using revised scope
  • Completely define new activities
  • Delete activities, if appropriate
  • Review and analyze revised budget
  • Reassess risks
  • Review the impact on the schedule of this change and determine revised planned completion date
  • Disseminate revised project details to team

Schedule a call now to learn more about Smart Projex



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Suzanne S. Davenport

Suzanne S. Davenport


Writes on project management, leadership, team building, and value delivery. Imagining work management in the future.