Marginalia

• Scope Control is the project immanent process of avoiding and integrating changes into the project scope baseline. In contrast to this Scope Verification is the process which determines whether the last valid and approved Scope Baseline is really met.

• The Scope Baseline is the collection of the Project Scope Statement, the WBS, and by the WBS Dictionary. Hence updating one of them includes an update of the Scope Baseline.

(2.5) Steuerung des Inhalts und Umfangs

(2.5.1) Process Input

... generated by predecessor processes:

(2.5.2) Process Definition

Scope Control is the process of "[...] controlling changes to the project scope" (comp. PMBOK3, p. 103). Naturally the project management has to manage scope changes too. The world is a collection of changes. Therefore changes are allowed. But they must be integrated into the existing project scope statement by refering to a defined change process. Undocumented 'by the way'-changes are not state of the art. Hence scope control is both: avoiding of "unaccepted" new workpackages and integrating "accepted" new workpackages into the project scope statement and/or into the WBS (comp. PMBOK3, p. 119)

The subject Scope operates on the base of other scope concerning concepts

(2.5.3) Tools and Techniques

PMBOK Mentioned Methods

  • A Change Control System is a documented process by which the scope can officially be changed
  • The Variance Analysis determines the causes of variances relative to the scope baseline
  • Replanning can be evoked by the approved change requests and may be realized by modifications of the WBS, the WBS Dictionary and so on.
  • The Configuration management system is a system for identifying releases of deliverables

(comp. PMBOK3, p. 121)

Open Source Tools

  • NN

(2.5.4) Process Output

  • Updates of the Project Scope Statement can be evoked by the approved change requests which are introduced as input of this process Scope Control
  • Updates of the WBS can be evoked by the approved change requests which are introduced as input of this process Scope Control
  • Updates of the WBS Dictionary can be evoked by the approved change requests which are introduced as input of this process Scope Control
  • Updates of the Scope Baseline can be evoked by the approved change requests which are introduced as input of this process Scope Control
  • Requested Changes can become necessary as result of the scope control
  • Recommended Corrective Action(s) can become necessary as result of the scope control
  • Updates of the Organizational Process Assets can be evoked by having lessons learned based upon the changes and their causes
  • Updates of the Project Management Plan may be evoked by the approved change requests

(comp. PMBOK3, pp. 121f)

(2.5.5) Output Using Successor Processes

Successors using the initially generated output as own input(1):

Processes using the updates as input(2):

  1. For details see FAQ::Q001:1
  2. For details see FAQ::Q001:2