126.96.36.199, 188.8.131.52 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.
184.108.40.206 Requirements Documentation
Requirements baseline; unambiguous (measurable and testable), traceable, complete, consistent, and
acceptable to key stakeholders.
220.127.116.11 Requirements Management Plan
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
18.104.22.168 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
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
In the project context, the term scope can refer to:
22.214.171.124 WBS Dictionary
May include quality requirements, acceptance criteria
5.5 Validate Scope
Process of formalizing acceptance for the completed product deliverables.
5.6 Control Scope
Completion of the product scope is measured against the product requirements.
126.96.36.199 Work Performance data
Contains measurements for technical performance.
11 Project Risk Management
Conduct risk management planning, identification, qualitative risk analysis, quantitative risk analysis,
response planning, response implementation, and monitoring risk
188.8.131.52 Project Management Plan Updates
Schedule baseline. Changes in the schedule baseline are incorporated in response to approved changes
in schedule estimates that may arise from agreed-upon risk responses.
Cost baseline. Changes in the cost baseline are incorporated in response to approved changes in cost
estimates that may arise from agreed-upon risk responses.
184.108.40.206 Data Analysis
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 may include weight, transaction times,
number of delivered defects, storage capacity, etc.
12 PROJECT PROCUREMENT MANAGEMENT
Project Procurement Management includes the processes necessary to purchase or acquire products, ….
from outside the project team. Project Procurement Management includes the management and control
processes required to develop and administer agreements such as contracts,…
220.127.116.11 PROJECT DOCUMENTS Project documents that can be considered as inputs to this process include
but are not limited to:
· Requirements documentation may include…technical requirements the seller is required to satisfy, and
· Requirements traceability matrix…links product requirements from their origin to the deliverables that
18.104.22.168 WORK PERFORMANCE DATA contains seller data on project status such as technical performance;
activities that have started, are in progress, or have completed; and costs that have been incurred or
22.214.171.124 WORK PERFORMANCE INFORMATION includes information on how a seller is performing by
comparing the deliverables received, the technical performance achieved, and the costs incurred and
accepted against the SOW budget for the work performed.
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
1. Technical requirements and requirements traceability matrix flowed down
2. Sellers technical performance status
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.