4.1.1.1, 5.2.3.1 Product scope description
This documents the characteristics of the product that the project will be undertaken to create.

Progressively elaborates the characteristics of the product, service or result described in the project charter and requirements documentation.

5.2.3.1 Requirements Documentation
Requirements baseline; unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders.

Components include:
Functional requirements
Non-functional requirements
Quality requirements
Acceptance criteria

5.1.3.2 Requirements Management Plan
Components include:

How requirements activities will be planned, tracked, and reported
Product metrics that will be used
Traceability structure to reflect which requirements attributes will be captured on the traceability matrix   

5.2.3.2 Requirements Traceability Matrix (RTM
Grid that links product requirements from their origin to the deliverables that satisfy them. It provides a means to track requirements throughout the project life cycle.

Includes tracing requirements for:

Project scope/WBS objectives
Product design
Product development
Test strategy and test scenarios

High-level requirements to more detailed requirements

Attributes associated with each requirement can be recorded in the RTM. Typical attributes used in the RTM may include current status (such as active, cancelled deferred, added, approved, completed), and acceptance criteria.


5 Scope

In the project context, the term scope can refer to:

  • Product scope - the features and functions that characterize a product
  • Project scope - the work performed to deliver a product...with the specified features and functions

5.3.3.2 WBS Dictionary
May include quality requirements, acceptance criteria


5.5 Validate Scope

Process of formalizing acceptance for the completed product deliverables.

8.3.1,4 Work Performance data
Can include planned vs. actual technical performance.

11 Project Risk Management

Conduct risk management planning, identification, qualitative risk analysis, quantitative risk analysis, response planning, and controlling risk 


11.6.2.4 Technical Performance Measurement (TPM)
TPM compares technical accomplishments during project execution to the schedule of technical achievement. It requires definition of objective quantifiable measures of technical performance which can be used to compare actual results against targets. Such TPMs might include weight, transaction times, number of delivered defects, storage capacity, etc. Deviation, such as demonstrating more or less functionality than planned at a milestone, can help to forecast the degree of success in achieving the project’s scope.

Project Management Institute {PMI)

Project Management Body of Knowledge (PMBOK® Guide) Excerpts 

Performance-Based Earned Value


Comparison of Deficiencies in ANSI-748 (EVMS Standard) compared with PMBOK® Guide:

  • Silent on "product" and "product baseline"
  • Silent on technical or capability requirements
  • Silent on "requirements traceability" to WBS
  • Cites "program work scope" instead of "technical work scope" or "product scope"
  • Silent on risk management


Dept. of Defense Instruction 5000.02, Operation of the Defense Acquisition System

ANSI-748 does not meet the needs of DoDI 5000.02, with regard to the above deficiencies.

A PDF file which compares ANSI-748 with PMBOK Guide®  for consistency with DoDI 5000.02 needs (applicable to the EMD phase) may be downloaded.