Page 144 -

5 - PROJECT SCOPE MANAGEMENT

• Stakeholder requirements, including:
○ Impacts to other organizational areas;

○ Impacts to other entities inside or outside the performing organization; and
○ Stakeholder communication and reporting requirements.

• Solution requirements, including:
○ Functional and nonfunctional requirements;

○ Technology and standard compliance requirements;
○ Support and training requirements;
○ Quality requirements; and

○ Reporting requirements, etc. (solution requirements can be documented textually, in models,
or both).
• Project requirements, such as:
○ Levels of service, performance, safety, compliance, etc.; and

○ Acceptance criteria.
• Transition requirements.

• Requirements assumptions, dependencies, and constraints.

5.2.3.2 requirements traceability Matrix

The requirements traceability matrix is a grid that links product requirements from their origin to the
deliverables that satisfy them. The implementation of a requirements traceability matrix helps ensure that each
requirement adds business value by linking it to the business and project objectives. It provides a means
to track requirements throughout the project life cycle, helping to ensure that requirements approved in the
requirements documentation are delivered at the end of the project. Finally, it provides a structure for managing
changes to the product scope.

Tracing includes, but is not limited to, tracing requirements for the following:

118 ©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Fifth Edition
®

Licensed To: Jorge Diego Fuentes Sanchez PMI MemberID: 2399412
This copy is a PMI Member benefit, not for distribution, sale, or reproduction.