Scope Management

Definition

Scope Management

the endeavor management task of properly managing the scope of an endeavor or center

Classification

As illustrated in the preceding figure, Scope Management is part of the following inheritance hierarchy:

• Type: Abstract
• Superclass: Endeavor Management Task
• Subclasses:
  • Endeavor Scope Management
  • Center Scope Management

Responsibilities

The typical responsibilities of Scope Management are to:

• Ensure the formal identification and establishment of the scope of the endeavor, application, or application version (typically by the requirements team).
• Ensure that each proposed change to the formally established scope is identified and documented (typically by the requirements team collaborating with the configuration management team).
• Ensure that each proposed scope change is analyzed in terms of its estimated impact on the endeavor’s cost, schedule, and probability of success (typically by the architecture team collaborating with the configuration management team and requirements team).
• Based on these impacts, either approve or disapprove the scope change(typically by the management team working with the client representatives).
• Ensure that each approved scope change is properly documented (typically by the requirements team).
• Thereby minimize or eliminate the risks due to unintended or unmanaged scope creep.

Preconditions

Scope management typically may begin when the following preconditions hold:

• Either the:
  • Endeavor has started.
  • Center exists.
• The management team is adequately:
  • Staffed.
  • Trained in scope management.

Completion Criteria

Scope management is typically complete when the following postconditions hold:

• Either the:
  • Endeavor has been completed.
  • Center has been retired.

Steps

Scope management typically involves the management team performing the following steps in an iterative, incremental, parallel, timeboxed, and ongoing manner:

• Determine Scope.
  Work with the customer representative and technical leader to negotiate and thereby determine the mission and objectives of the endeavor or center.
• Specify Scope.
  Work with the requirements team to ensure the proper specification of the scope (e.g., in terms of mission statement, vision statement, requirements specifications).
• Continuously Evaluate Scope.
  Work with the change control board, requirements team, and architecture team to continuously evaluate the scope.
• Control Scope.
  Work with the customer representative change control board, requirements team, and architecture team to ensure that:
  • The requirements of associated application(s) are well defined ( requirements specification) and controlled ( configuration control) so that they only change or increase (i.e., scope creep) when authorized (e.g., by the change control board).
  • Only those work products are produced and those work units are performed that are cost-effective and actually required to meet the mission’s objectives and to fulfill its associated requirements.

Techniques

Scope management typically involves the following techniques:

• Close collaboration with stakeholders.
• Process guidelines.
• Configuration control.
• Documentation iteration.

Work Products

Scope management results in the production and/or iteration of the following work products to document changes in scope:

• Management Set:
  • Contract
  • Statement Of Work
  • Work Breakdown Structure
  • Mission Statement
• Requirements Set:
  • Application Vision Statement
  • System Requirements Specification

Guidelines

• Lack of scope management is one of the most common reasons of project and program failure.
• Scope management is one of the most important responsibilities of a management team.