Response: Certainly, Avi. One notable project where I effectively managed requirements was during the development of an HVAC product selection software for Johnson Controls Hitachi. In this project, I used JIRA for managing the product backlog and tracking user stories, while Confluence was used for documentation and collaboration. To ensure traceability, I made sure that each requirement was linked to specific user stories, acceptance criteria, and business objectives. This allowed us to track the progress and impact of each requirement throughout the project lifecycle. For change control, we had a structured process in place where any changes were reviewed in sprint planning meetings, prioritized based on business value, and approved by stakeholders before being implemented. Regular sprint reviews and backlog refinement sessions helped in maintaining alignment with the project’s goals and ensured that all stakeholder needs were addressed comprehensively.