Control scope change

The purpose of this competency is to achieve the goals of change control, i.e. to:

capture stakeholders’ requests to make changes to scope;
ensure that requests are only approved if viable and achievable;
integrate changes into the existing scope.

Performance criteria

You must be able to:

plan and initiate change control
capture and assess change requests
decide whether to accept change requests
implement accepted change requests
keep stakeholders informed
take action to manage any issues that arise
assure the quality of change control

This competency is closely linked to configuration management.

On complex projects and programmes the two functions will probably be performed by the different people and it will be appropriate to have separate competencies for controlling scope change and managing the configuration.

On simpler projects it may be better to combine them into a single competency for inclusion in a role that is responsible for both.

Knowledge and understanding

You need to know and understand:

the principles and goals of change control
responsibilities for change control
the context of the work and its impact on controlling scope change
a procedure for change control
the purpose and content of change control documentation
the types of change requests that may emerge
the reasons for scope change
the need to record project changes and the impact of such changes on delivery plans
the importance of communicating decisions to stakeholders
the issues that may emerge and how these can be managed
how assurance applies to change control

Please consider allowing cookies to be able to share this page on social media sites.