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:

  1. plan and initiate change control
  2. capture and assess change requests
  3. decide whether to accept change requests
  4. implement accepted change requests
  5. keep stakeholders informed
  6. take action to manage any issues that arise
  7. 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:

  1. the principles and goals of change control
  2. responsibilities for change control
  3. the context of the work and its impact on controlling scope change
  4. a procedure for change control
  5. the purpose and content of change control documentation
  6. the types of change requests that may emerge
  7. the reasons for scope change
  8. the need to record project changes and the impact of such changes on delivery plans
  9. the importance of communicating decisions to stakeholders
  10. the issues that may emerge and how these can be managed
  11. how assurance applies to change control



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

Change cookie settings
No history has been recorded.
Back to top