Requirements status during the project development cycle is the information that should be reported to the stakeholder who wants to know how the implementation of new features in the development of a product is progressing. The requirements status shows how many requirements are in each stage of the development cycle, such as analysis, design, development, testing, or deployment. This information can help the stakeholder understand the progress and quality of the product development and identify any issues or risks that may affect the delivery of the new features. Distribution of project changes is not relevant to the implementation of new features, as it shows how many changes have been requested, approved, or rejected for the project scope, schedule, cost, or quality. Number of requirements approved vs. number of requirements rejected is not relevant to the implementation of new features, as it shows how many requirements have been accepted or discarded by the stakeholders during the requirements analysis phase. Number of requirements tested and approved is not sufficient to report the implementation of new features, as it only shows how many requirements have passed the verification and validation process, but not how many are still in development or deployment stages. References: Business Analysis for Practitioners: A Practice Guide, page 161-162; PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline, page 19.

The system requirements verification matrix is a tool that helps to track the status of each requirement throughout the project lifecycle. It shows whether a requirement has been accepted, rejected, deferred, or implemented. The business analyst should have used this tool to record the reasons for rejection or deferral of any requirement, as well as the impact and resolution of such changes. This way, the business analyst can easily provide a list of rejected and deferred requirements to the project manager upon request. Setting up a change control board is not enough to track the number of rejections, as it does not provide a detailed record of each requirement's status. Limiting the number of rejected requirements on the project is not a realistic or helpful approach, as some requirements may be invalid, incomplete, or conflicting and need to be rejected or deferred for the benefit of the project. Spending more time up-front reviewing the requirements may reduce the chances of rejections, but it does not guarantee that no requirement will be rejected or deferred later in the project. References: Business Analysis for Practitioners: A Practice Guide, page 161-162; PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline, page 19.