Purpose:

Define Scope is the process of developing a detailed description of the project and product. The key benefit of this process is that it describes the product, service, or result boundaries by defining which of the requirements collected will be included in and excluded from the project scope.

Objective:

Develop a detailed description of the project and product.

Description:

Since all of the requirements identified in Collect Requirements may not be included in the project, the Define Scope process selects the final project requirements from the requirements documentation delivered during the Collect Requirements process. It then develops a detailed description of the project and product, service, or result.

The preparation of a detailed project scope statement is critical to project success and builds upon the major deliverables, assumptions, and constraints that are documented during project initiation. During project planning, the project scope is defined and described with greater specificity as more information about the project is known. Existing risks, assumptions, and constraints are analyzed for completeness and added or updated as necessary. The Define Scope process can be highly iterative. An iterative life cycle projects, a high-level vision will be developed for the overall project, but the detailed scope is determined one iteration at a time, and the detailed planning for the next iteration is carried out as work progresses on the current project scope and deliverables.

Inputs:

  • Scope Management Plan
  • Project Charter
  • Requirements Documentation

Outputs:

  • Project Scope Statement
  • Updated Project Documents

Controls:

  • Project Charter Template
  • Project Charter Summery Template
  • Expert Judgment
  • Product Analysis
  • Alternatives Generation
  • Facilitated Workshops

Task Instructions:

Document Project Scope

    1. Using the Project Charter Template, Process Design Summary Document and Approved Business Case,  <?>, [the Project Manager] with support from [the Project Champion] is responsible for discussing and defining the scope of the project, which needs to clearly establish the problem statement of the system to be developed.