The change control process is a set of procedures and tools that are used to manage changes to the requirements and the solution throughout the project life cycle. The change control process is defined in the business analysis plan, which is a document that describes how the business analysis activities will be performed, monitored, and controlled. The business analysis plan also specifies the roles and responsibilities of the business analyst and other stakeholders involved in the change control process. The business analyst should follow the change control process as defined in the business analysis plan to ensure that any changes to the requirements are properly documented, analyzed, approved, communicated, and implemented. By following the change control process, the business analyst can avoid scope creep, maintain the quality and integrity of the requirements, and align the solution with the business needs and objectives. References: PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline1, page 24; Business Analysis for Practitioners: A Practice Guide2, page 133.

The first thing the business analyst should do immediately after the discussion with the project manager is to schedule time with the process owners. The process owners are the people or groups responsible for a specific business process or procedure that is affected by the project5. The business analyst needs to understand the current state of the processes, the pain points and opportunities, the requirements and expectations, and the impact of the project on the processes. By meeting with the process owners, the business analyst can establish a relationship, gather relevant information, and ensure alignment and collaboration. Putting the information into a project plan is premature, as the business analyst needs to conduct more analysis and planning before creating a project plan. Developing an issues log is not necessary, as there are no issues identified at this stage. Assessing the risks for the project is important, but it is not the immediate action, as the business analyst needs to understand the scope and objectives of the project first. References: PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline2, PMI Guide to Business Analysis3, Business Analysis for Practitioners: A Practice Guide4, What is a Process Owner? Definition & Responsibilities

A matrix is a tool that can be used to record, organize, and track the requirements throughout the lifecycle of the project. A matrix can help the business analyst to identify the sources, dependencies, relationships, and attributes of the requirements, as well as to monitor their status, changes, and traceability. A matrix can also facilitate the communication, verification, and validation of the requirements with the stakeholders, and ensure their alignment with the business needs and objectives. A matrix can be updated and reviewed regularly to reflect the current state of the requirements and the solution, and to obtain the approval and acceptance from the stakeholders. A common example of a matrix is the Requirements Traceability Matrix (RTM), which is a tool that links the requirements to the project scope, objectives, deliverables, and test cases12. References: PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline3, page 18; Business Analysis for Practitioners: A Practice Guide4, page 92.

A functional requirement is a requirement that specifies what the system should do or how it should behave under certain conditions. A functional requirement describes the functionality, behavior, or performance of the system. An example of a functional requirement is the system is able to require passwords, which defines a security feature of the system that prevents unauthorized access. References: PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline1, page 17; Business Analysis for Practitioners: A Practice Guide2, page 92.

According to the PMI Guide to Business Analysis, a requirements review is a formal meeting where the requirements are presented and evaluated by the stakeholders, subject matter experts, and other relevant parties. The purpose of the review is to ensure that the requirements are clear, complete, consistent, feasible, testable, and aligned with the business needs and objectives. To prepare for the review, it would be best for the team to evaluate the requirements and highlight those that cannot be met or need to be deferred, as this would help to identify any gaps, risks, issues, or dependencies that need to be addressed or resolved before proceeding to the design phase. Preparing a test procedure, starting the design, or requesting a contract amendment are not appropriate actions to take before the review, as they could introduce errors, biases, or conflicts in the requirements. References: PMI Guide to Business Analysis, page 181-182.