Which document is often utilized to track requirements changes?

The change log is a crucial document in the requirements life cycle management process, as it serves to systematically track alterations to requirements throughout the project. This log captures critical information about each change, such as the rationale behind the modification, the date it occurred, what requirements were affected, and the person responsible for the change.

Utilizing a change log helps ensure transparency and traceability in the management of requirements, allowing the team to understand how the project has evolved over time. It is an essential tool for maintaining alignment among stakeholders, facilitating communication regarding any adjustments, and helping assess the impact of changes on the overall project scope, timeline, and objectives.

Other documents, while important in their own right, do not specifically focus on tracking changes to requirements. A risk management plan deals with identifying and mitigating risks, a project schedule outlines the timeline and milestones of project tasks, and a budget report focuses on financial tracking and management. These documents serve different purposes and do not provide the same structured approach to recording changes in requirements as a change log does.