Section: Volume D
Explanation:
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:
Business needs, opportunities, goals, and objectives;

Project objectives;

Project scope/WBS deliverables;

Product design;

Product development;

Test strategy and test scenarios; and

High-level requirements to more detailed requirements.

Attributes associated with each requirement can be recorded in the requirements traceability matrix. These attributes help to define key information about the requirement. Typical attributes used in the requirements traceability matrix may include: a unique identifier, a textual description of the requirement, the rationale for inclusion, owner, source, priority, version, current status (such as active, cancelled, deferred, added, approved, assigned, completed), and status date. Additional attributes to ensure that the requirement has met stakeholders' satisfaction may include stability, complexity, and acceptance criteria.

Explanation/Reference:
Explanation:
Process: 6.7 Control Schedule
Definition: Control Schedule is the process of monitoring the status of project activities to update project progress and manage changes to the schedule baseline to achieve the plan.
Key Benefit: The key benefit of this process is that it provides the means to recognize deviation from the plan and take corrective and preventive actions and thus minimize risk.
Inputs
1. Project management plan
2. Project schedule
3. Work performance data
4. Project calendars
5. Schedule data
6. Organizational process assets
Tools & Techniques
1. Performance reviews
2. Project management software
3. Resource optimization techniques
4. Modeling techniques
5. Leads and lags
6. Schedule compression
7. Scheduling tool
Outputs
1. Work performance information
2. Schedule forecasts
3. Change requests
4. Project management plan updates
5. Project documents updates
6. Organizational process assets updates

Explanation/Reference:
Explanation:
Process: 9.3 Develop Project Team
Definition: The process of improving competencies, team member interaction, and overall team environment to enhance project performance.
Key Benefit: The key benefit of this process is that it results in improved teamwork, enhanced people skills and competencies, motivated employees, reduced staff turnover rates, and improved overall project performance.
Inputs
1. Human resource management plan
2. Project staff assignments
3. Resource calendars
Tools & Techniques
1. Interpersonal skills
2. Training
3. Team-building activities
4. Ground rules
5. Colocation
6. Recognition and rewards
7. Personnel assessment tools
Outputs
1. Team performance assessments
2. Enterprise environmental factors updates