The business analyst receives multiple changes from different stakeholders during the requirements gathering phase of a project. How should the business analyst track the requirements throughout the lifecycle of the project to secure the delivery of the expected solution?

The core task described is tracking requirements and managing changes from multiple stakeholders throughout the project lifecycle. This is the primary function of a requirements traceability matrix. This matrix captures key requirement attributes and links requirements to their origin, business objectives, and downstream deliverables like design, code, and test cases. Regularly reviewing this matrix with stakeholders and gaining approval for the baseline and any changes ensures that the final solution aligns with the agreed-upon needs and that all requirements are addressed.

A. Inspections are a quality control activity to find defects in deliverables, not a method for tracking requirements throughout the entire lifecycle.
B. Meetings are a communication tool. While essential for discussing changes, they are not the tracking mechanism itself, which is typically a formal document or tool.
C. A risk traceability matrix is used to track project risks, not project requirements. This is a misuse of the tool's name and purpose.

- Project Management Institute. (2017). Business Analysis for Practitioners: A Practice Guide. Section 7.1, p. 131. "Traceability is the process of tracking requirements from their origin to their final implementation... A requirements traceability matrix is a common tool used to perform this function."

- Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Section 5.2.3.2, p. 148-149. Describes the Requirements Traceability Matrix as an output of the Collect Requirements process used to track requirements throughout the project life cycle.