Scope Verification is not Quality Control: quality control is 'only' concerned "[...] with meeting the quality requirements specified for the deliverables"

Scope Verification is not Scope Control: Although the stakeholders of the project owner might control whether the requirements have been fullfilled and the scope has been met, that kind of 'controlling' is part of the scope verification. And the 'real' scope control is the management of (wished or unwished) scope changes during the actual project work.

• It's a little surprise. But the PMBOK definitely says, that Scope Verification only takes the WBS Dictionary as input, not the the WBS itself (comp. PMBOK3, p. 105 and 118)

• The success of a project is the raisonable satisfaction of the project owner and his stakeholders. If the project owner doesn't think and speak about their project as a success, the project is not successful, even if in fact all requirements have exactly been fullfilled. Organizing and guiding a positive communication is an intrinsic task of the project.

(2.4) Scope Verification

(2.4.1) Process Input

... generated by predecessor processes:


(2.4.2) Process Definition

Scope Verification is the process  by which the project manager gets "[...] the formalized acceptance of the completed project deliverables " (comp. PMBOK3, p. 103).  The scope of the project in its inherent sense is the work, that must be done to met the required targets. But whether the work has sucessfully been done or not can only be measured by comparing the generated targets of the project with the required targets. Nevertheless, scope verification is "obtaining the stakeholders' formal acceptance" by commonly "[...] reviewing the deliverables to ensure that each is completed satisfactorily" (comp. PMBOK3, p. 118).

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

(2.4.3) Tools and Techniques

PMBOK Mentioned Methods

  • Inspection is the investigation whether the work and its results (deliverables) meets the requirements and the acceptence criteria (comp. PMBOK3, p. 119)

Open Source Tools

  • NN



(2.4.4) Process Output

  • Accepted Deliverables in case of success
  • Requested Changes in case of failure
  • Recommended Corrective Aactions in case of failure

(2.4.5) Output Using Successor Processes

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

  1. For details see FAQ::Q001:1