In the middle of a project, a new requirement was added to the scope. The business analyst must determine if any impacts, dependencies, or risks are associated with the addition to the scope. What task should the business analyst perform in order to identify these impacts?

When a new requirement is added, its relationships with existing requirements, business objectives, and solution components must be understood to assess the full impact. Managing requirements traceability involves creating and using a requirements traceability matrix. This matrix is the primary tool for identifying these relationships, allowing the business analyst to effectively trace the dependencies and potential impacts of the change across the project, thereby uncovering associated risks.

A. Manage solution scope: This is a broader process; traceability is a specific task within it used to perform the impact analysis.
C. Manage requirements prioritization: Prioritization occurs after the impact of the new requirement is understood, not as a means to identify it.
D. Manage assumptions and constraints: While the new requirement might affect assumptions, traceability is the direct task used to identify impacts and dependencies.

- Project Management Institute. (2017). The PMI Guide to Business Analysis. Section 5.1, Trace Requirements, p. 148. "The purpose of Trace Requirements is to ensure that requirements and designs at different levels are aligned to one another and to manage the effects of change to one level on related levels."

- Project Management Institute. (2017). Business Analysis for Practitioners: A Practice Guide. Section 5.4, Traceability and Monitoring, p. 87. "Traceability helps in performing an impact analysis by providing a view of all the requirements that will be impacted by a proposed change."