|Español - Italiano|
- capture stakeholders’ requests to make changes to scope;
- ensure that requests are only approved if viable and achievable;
- integrate changes into the existing scope.
|Indicators||Level 2 attributes|| |
Scope change requests can apply to any objective, i.e. outputs, outcomes or benefits.
Change control is most easily applied to outputs and physical products in particular.
Where the change control procedure is applied more broadly to benefits there must be evidence that all consequences for business as usual, change management activity and the business case have been considered.
Change requests are submitted and logged.
All change requests are reviewed against high level objectives and stakeholders informed of results.
All change requests that pass the review are assessed.
A decision is made and documented for all assessed requests.
All approved changes are implemented.
Stakeholders who originate requests are informed of the final decision.
|Indicators||Level 3 attributes|
Change requests are submitted and logged in a consistent format fully describing the nature of, and reason for the change.
All change requests are reviewed for consistency with high level objectives.
Changes that are not consistent with high level objectives are rejected.
All change requests that pass the review are objectively assessed in detail for their viability, desirability and practicality.
Recommended action is documented and submitted for a decision.
A group or individual has clear accountability and responsibility for the final decision.
Decisions for assessed requests are made in a timely manner.
Approved changes are built into all scope and delivery documentation.
Stakeholders who originate requests are kept informed of progress and the rationale behind the decision.
All relevant stakeholders are kept up to date with scope changes.