Page 79 -

5 - PROJECT SCOPE MANAGEMENT

Initially, in predictive life cycle software projects, there is an attempt to develop a set of software requirements
that is complete, correct, consistent, and detailed. The requirements provide the basis for determining the scope
of the project and for developing the WBS and the work packages. Project scope is then managed by controlling
changes to the software requirements and the work activities needed to implement those requirements. The impact
of changes to product requirements on the project schedule, budget, resources, and technology may require revision
of the project scope and is reflected in changes to the WBS. Change control boards and a version control system
are typically utilized in predictive life cycle software projects to manage the changing scope of a software project.

5.2.1 Collect Requirements: Inputs

The inputs for collecting requirements in Section 5.2.1 of the PMBOK Guide are applicable to collecting
®
requirements for software projects.

5.2.1.1 Scope Management Plan

®
See Section 5.2.1.1 of the PMBOK Guide.

5.2.1.2 Requirements Management Plan

See Section 5.2.1.2 of the PMBOK Guide.
®

5.2.1.3 Stakeholder Management Plan

See Section 5.2.1.3 of the PMBOK Guide.
®

5.2.1.4 Project Charter

See Section 5.2.1.4 of the PMBOK Guide.
®

5.2.1.5 Stakeholder Register

See Section 5.2.1.5 of the PMBOK Guide.
®

5.2.2 Collect Requirements: Tools and Techniques

®
The tools and techniques in Section 5.2.2 of the PMBOK Guide are applicable tools and techniques for collecting
requirements for both predictive and adaptive software projects with the indicated adaptations and extensions.
Persona modeling is also used as a tool for collecting software requirements. See Section 13 of this Software
Extension.

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