Page 107 - The Six Sigma Project Planner

*
Scope Change Control Plan
Project scope management describes the processes required to ensure that the project
includes all the work required and only the work required to complete the project
successfully. It consists of initiation, scope planning, scope definition, scope verification,
and scope change control (Duncan, 1996, page 6). This section of The Six Sigma Project
Planner addresses scope change control; the other subjects addressed by scope
management are covered in earlier sections of the Planner.
The scope change control plan addresses how scope changes will be identified,
classified, and integrated into the project. Scope change almost always involves either
scope creep (the tendency for a project’s scope to grow beyond the original scope) or scope
drift (the tendency for a project’s scope to change unintentionally over time). Scope
creep diverts resources from the project’s authorized scope. Both scope creep and scope
drift create a lack of focus on the project’s authorized goals and deliverables. These are
serious issues for the project team; project failure due to poor scope change control is
very common.
Inputs to the scope change control plan include:
• Project charter (pp. 2-3)

• WBS (p. 29)
• Issues lists (Appendix, p. 200, Worksheet 71)
• Quality plan items (p. 80)

• Budget reports (pp. 84-85)
• Project schedule (p. 49)
• Change requests (p. 206)

The team should review the above documents before creating the scope change control
plan. The outputs of this activity are the scope change control plan, scope change
reports, and corrective action. The change control plan should include periodic review
of activity audit reports, issues lists, performance reports (quality, cost, and schedule),
and change requests.

Change Control System
The Project Management Body of Knowledge defines a change control system as:
“A collection of formal, documented procedures that defines the steps by which
official project documents may be changed. It includes the paperwork, tracking
systems, and approval levels necessary for authorizing changes.”
In developing change control systems, project teams are advised to look to their
organization’s own policies and procedures for guidance. Nearly all but the smallest
organizations have systems in place for ensuring that policy and procedure changes are

*
Part of the official project plan.

90