Page 91 -

5 - PROJECT SCOPE MANAGEMENT

5.5.1.2 Requirements Documentation

See Section 5.5.1.2 of the PMBOK Guide.
®

5.5.1.3 Requirements Traceability Matrix

See Section 5.5.1.3 of the PMBOK Guide.
®

5.5.1.4 Verified Deliverables

See Section 5.5.1.4 of the PMBOK Guide.
®

Inputs for verification may include formally documented requirements, one or more requirements traceability
matrices, design documentation, and the software code, all of which may be updated incrementally as they evolve
during iterative cycles. In some cases, a suite of development work products including the technical specifications,
design documentation, traceability matrices, test plans, and test results, as maintained in automated application
life-cycle management systems, may also be inputs for verification of scope.

5.5.1.5 Work Performance Data

See in Section 5.5.1.5 of the PMBOK Guide.
®

5.5.1.6 Inputs for Adaptive Software Projects

For adaptive life cycle software projects, validation occurs incrementally during and at the end of iterative cycles
that produce working deliverable increments of the software product; the inputs are the test cases, test scenarios,
and demonstration scenarios developed before and during each iteration cycle. Additional inputs for validating
the scope of an adaptive life cycle software project may include formally documented requirements, one or more
requirements traceability matrices, design documentation, and the software code, all of which may be updated
incrementally as they evolve during iteration cycles. A formal validation plan may be developed initially and applied
throughout the project life cycle, or validation may be an element that is built into each iterative cycle without a
formal validation plan.

5.5.2 Validate Scope: Tools and Techniques

The tools and techniques for validating scope in Section 5.5.2 of the PMBOK Guide are applicable for validating
®
the scope of both predictive and adaptive software projects. Product scope can be validated using analysis, reviews,
acceptance testing, and demonstrations. Reviews include formal inspections, peer reviews of working software,
management reviews of validation status, and reviews with external stakeholders. Test-driven development (TDD)
is a method of validating the scope of small increments of software. TDD is described in conjunction with Figure 2-6
and in Section 9.2.3.8 of this Software Extension.

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