Page 83 -

5 - PROJECT SCOPE MANAGEMENT

5.3.2 Define Scope: Tools and Techniques

The tools and techniques listed in Section 5.3.2.1 through 5.3.2.4 are applicable for defining the scope of
software project and product.

5.3.2.1 Expert Judgment

See Section 5.3.2.1 of the PMBOK Guide.
®

5.3.2.2 Product Analysis

See Section 5.3.2.2 of the PMBOK Guide.
®

5.3.2.3 Alternatives Generation

See Section 5.3.2.3 of the PMBOK Guide.
®

5.3.2.4 Facilitated Workshops

®
See Section 5.3.2.4 of the PMBOK Guide.

5.3.3 Define Scope: Outputs

The outputs for defining scope in Section 5.3.3 of the PMBOK Guide are applicable outputs from defining
®
software project and product scope. Section 5.3.3.3 of this Software Extension presents additional considerations
for defining scope output for adaptive life cycle software projects.

5.3.3.1 Project Scope Statement

See Section 5.3.3.1 of the PMBOK Guide.
®

5.3.3.2 Project Documents Updates

See Section 5.3.3.2 of the PMBOK Guide.
®

5.3.3.3 Additional Considerations

For an ideal predictive life cycle software project, the initial project and product scope statement is a static document,
although this is rarely the case in practice. In an adaptive life cycle software project, the scope statement is planned to be
an evolving document that is bounded by overall project scope constraints. Planning for systematic evolution of project
and product scope is a primary factor that distinguishes adaptive software project life cycles from predictive life cycles.

72 ©2013 Project Management Institute. Software Extension to the PMBOK Guide Fifth Edition
®