Why Your Change Management Never Works Out the Way You Plan And How You Can Make It Work
While change can have a significant impact on a project, lot of effort would have gone into discussing what is needed and what needs to be accomplished.
Changes are certain in any projects, be it small or big in nature. Handling change requests are always a challenge to project managers as it may lead to adverse impact to project’s performance.It is recommended that a change request should undergo various processes to get it approved as genuine during project management life cycle. Apart from getting it approved, the implementation of approved change requests is also a key responsibility of the project manager.
A project manager should always stand as a barricade and avoid unnecessary changes to the project.
The project managers need to be proactive as they also need to analyze the origin of the changes & prevent future changes from thereof. There are project constraints in all projects and a change to one of the project constraint will impact other constraints by default.
A change can be triggered at any point in a project and we cannot restrict it. A change, which is requested during development/execution stage of a project will cost more to the project than requesting it in the initial / requirements gathering stage.
That’s why the project managers are supposed to be serious about changes and they cannot treat changes casually during project life cycle.
As per PMBOK 5th edition, the following processes have ‘Approved Change Requests/ Change requests’ as input and output and these processes are part of executing, monitoring & controlling process groups.
- Direct and Manage project work – Approved change request as input & Change request as output
- Monitor and control project work – Validate changes as input & Change request as output
- Perform Integrated change control – Change requests as input & Approved change request as output
- Validate scope – Change requests as output
- Control scope – Change requests as output
- Control schedule – Change requests as output
- Control cost – Change requests as output
- Perform Quality assurance – Change requests as output
- Control quality – Approved change requests as input and change requests as output
- Manage project team – Change requests as output
- Control communications – Change requests as output
- Control risks – Change requests as output
- Plan procurement management – Change requests as output
- Conduct procurements – Change requests as output
- Control procurements – Approved change requests as input and change request as output
- Manage stakeholder engagement – change requests as output
- Control stakeholder engagement – change requests as output
To know more on Project Management or to Learn PMP Concepts, visit the PMP Course on ApnaCourse.