Enterprise environmental factors in this context refer to the external rules and conditions "[...] that could affect how project scope is managed", for example "organization's culture, infrastructure, tools, human resources, personnel policies, and marketplace conditions" (comp. PMBOK3, page 107).

• And Organizational process assets in this context refer to "[...] the formal an informal policies, procedures, and guidelines, that could impact how the project's scope is managed" (comp. PMBOK3, page 107)

• Scope Planning is the process of planning the process of defining (and ensuring) the scope. It is NOT the process of defining (and ensuring etc.) the scope itself.

• The output of this process is not only used by processes of the planning process group. Therefore it also builds a bridge (= the jumping platform) into the processes of other Process Groups

(2.1) Scope Planning

(2.1.1) Process Input

... generated by predecessor processes

... introduced by external units

  • Enterprise environmental factors
  • Organizational process assets

(2.1.2) Process Definition

Scope Planning is the process which generates the Project Scope Management Plan. And this Project Scope Management Plan (which itself naturally is part of the project management plan) "[...] documents how the project scope will be defined, verified, controlled, and how the work break down structure (WBS) will be created and defined " (comp. PMBOK3, p. 103)

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

(2.1.3) Tools and Techniques

PMBOK Mentioned Methods

  • Expert judgement in this case means expert knowledge about "[...] equivalent projects have managed scope"
  • Templates, forms, standards which are given to the project (manager) for being respected and used.

(comp. PMBOK3, p. 108)

Open Source Tools

  • NN

(2.1.4) Process Output

  • The Project Scope Management Plan "[...] provides guidance on how the project scope will be defined, documented, verified, managed, and controlled [...]". It should include a description / definition how ...
    • the Preliminary Project Scope Statement shall be elaborated and transformed into the more detailed Project Scope Statement
    • the Work Breakdown Structure (WBS) shall be generated and updated on the base of the Project Scope Statement, its refinements and/or approved (scope) changes
    • the "[...] formal verification and acceptance of completed project deliverables will be obtained"
    • the "[...] requests for changes to the detailed project scope statement will be processed"

(comp. PMBOK3, p. 108)

(2.1.5) Output Using Successor Processes

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

  1. For details see FAQ::Q001:1