How the Program Scope impacts on Change Management
The PMP scope outlines:
-
What systems, processes, teams, and business units are affected
-
What is being introduced, upgraded, removed, or restructured
This informs change management:
-
Who needs to change (stakeholders, teams, users)
-
What behaviors, mindsets, or skills need to shift
-
When these changes will happen, aligned with delivery phases
The project scope highlights areas of organisational change, like:
-
A new software interface
-
Role restructuring
-
Automated workflows replacing manual tasks
- Integrations and interfaces
From this, change management plans:
-
Stakeholder mapping
-
Impact assessments
-
Communication strategies
If the project scope includes:
-
Deployment of a new platform, tool, or interface
-
Migration to a new system or cloud-based solution
-
Introduction of automated workflows or business process changes
Then Change Management must:
-
Design and deliver appropriate training materials for different user groups
-
Create user support resources, such as quick reference guides, FAQs, or e-learning modules
-
Ensure support channels (e.g. helpdesk, peer champions) are ready to handle queries post-implementation
Most transformation projects are phased, with scope broken into deliverables over time.
Change Management is aligned to those phases:
-
Early adopters or pilot groups first
-
Wider rollout supported by waves of communication and readiness activities
-
Post-go-live reinforcement tied to scope completion
If the project scope aims to:
-
Improve operational efficiency
-
Reduce manual processes or legacy system dependencies
-
Enhance system usability or user experience
Then Change Management should track:
-
Adoption and usage metrics
-
User satisfaction and feedback
-
Evidence of behavioral or process changes aligned with the intended project outcomes
When you are reviewing the program scope in the Project Management Plan, take into consideration the above populating the programme Scope section in the CIP.
