Page 78 -

5 - PROJECT SCOPE MANAGEMENT

both cases. As described in Section 2.4 of this Software Extension, development iterations and product increments
are independent factors.

5.1.2 Plan Scope Management: Tools and Techniques

®
The tools and techniques in Section 5.1.2 of the PMBOK Guide can be used to plan scope management for both
predictive and adaptive life cycle software projects.
5

5.1.2.1 Expert Judgment

®
See Section 5.1.2.1 of the PMBOK Guide.

5.1.2.2 Meetings

See Section 5.1.2.2 of the PMBOK Guide.
®

5.1.3 Plan Scope Management: Outputs

The outputs for planning scope management of a software project include the scope management plan and the
requirements management plan, as indicated in Section 5.1.3 of the PMBOK Guide. In addition, the project plan
®
may include a release plan (see 5.1.1.5 of this Software Extension).

5.1.3.1 Scope Management Plan

See 5.1.3.1 of the PMBOK Guide.
®

5.1.3.2 Requirements Management Plan

See 5.1.3.2 of the PMBOK Guide.
®

5.2 Collect Requirements

®
The inputs, tools and techniques, and outputs for Collect Requirements in Section 5.2 of the PMBOK Guide are
applicable for collecting requirements for software projects.

The Collect Requirements process is often referred to as “Elicit Requirements” in software engineering.
Software requirements provide the basis for establishing project and product scope and for determining needed
resources. Requirements are collected (elicited), to the extent possible, during the initiation and planning phases
of all software projects. Additional requirements may emerge, especially during the iterative cycles of adaptive
software project life cycles [19].

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