Page 92 -

5 - PROJECT SCOPE MANAGEMENT

Ideally, a software test involves preparation of test inputs, test conditions, and an objective statement of the
desired test results; execution of the test in a specified environment under specified conditions; and observation and
recording of the test results. A validation demonstration differs from a validation test in that a test has objectively
stated success criteria, whereas a demonstration relies on the subjective observations of witnesses to determine
the success or failure of the demonstrated software features.

For predictive life cycle software projects, validation of product scope is a major phase that occurs at the end of
developing a product increment and during software delivery. For adaptive life cycles, continuous validation occurs
during and at the end of each iteration cycle. A major validation effort may accompany delivery of the final product 5
at the end of the final iteration cycle. A formal validation plan may be developed initially and applied throughout an
adaptive project life cycle, or validation may be an element that is built into each iterative cycle without a formal
validation plan.

5.5.2.1 Inspection

See Section 5.5.2.1 of the PMBOK Guide.
®
A software inspection is a formalized review process that involves preparation for the inspection; roles to
be played by the inspectors; checklists and forms; a moderated meeting; and documented follow-up activities.
A software inspection differs from a software walkthrough in the formality of the inspection process, including
record keeping, and the systematic follow-up to ensure that defects discovered during an inspection are fixed [16
(p. 289–298 and Appendix 7B)].

5.5.2.2 Group Decision-Making Techniques

See Section 5.5.2.2 of the PMBOK Guide.
®
For adaptive life cycle software projects, validation of scope for tested, deliverable product increments occurs
by group decision-making of the customer, user representatives, and other stakeholders, as appropriate.

5.5.3 Validate Scope: Outputs

®
The outputs for Validate Scope in Section 5.5.3 of the PMBOK Guide are applicable outputs for validating the
scope of a software project with the following clarifications.

5.5.3.1 Accepted Deliverables

See Section 5.5.3.1 of the PMBOK Guide.
®
Adaptive life cycle software projects produce validated, deliverable software at the end of each iteration cycle
that produces a working demonstrable product increment. A customer may choose to accept delivery of some, all,
or none of the intermediate deliverables of an adaptive life cycle project.

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