An interview is a technique that involves a structured or unstructured conversation between the business analyst and one or more stakeholders to elicit information, opinions, or feedback about a topic. An interview can be conducted face-to-face, over the phone, or through other communication channels. An interview can be prepared in advance with a list of questions or topics to cover, or it can be spontaneous and flexible. An interview can be used to explore the needs, expectations, preferences, or concerns of the stakeholders, as well as to clarify, verify, or validate the requirements. An interview is suitable for a project involving a low number of stakeholders, as it allows the business analyst to establish rapport, ask probing questions, and obtain detailed and specific information from each stakeholder. References: PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline1, page 17; Business Analysis for Practitioners: A Practice Guide2, page 89.

A user survey is a technique that can be used to determine how well the solution meets the business case. A user survey is a method of collecting feedback from the end users of the solution about their satisfaction, preferences, expectations, needs, problems, or suggestions. A user survey can help to measure the performance, quality, usability, and value of the solution and compare it with the expected benefits and outcomes defined in the business case. A user survey can also help to identify areas for improvement or enhancement of the solution. Asking the sponsor for feedback is not sufficient to determine how well the solution meets the business case, as it does not capture the perspective of the end users who are directly affected by the solution. Surveying the project is not relevant to this scenario, as it does not focus on the solution but rather on the project management processes and practices. Comparing the results of day-in-the- life (DITL) testing and integration testing is not effective, as it does not reflect the actual usage and experience of the solution by the end users after deployment. References: PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline1, page 14; Business Analysis for Practitioners: A Practice Guide2, page 80.

Explanation/Reference: https://www.pumpsandsystems.com/general-scope-document-project-boundaries

According to the PMI Guide to Business Analysis, a use case is a technique that describes how an actor interacts with a system or a process to achieve a specific goal. A use case can help to prevent problems from occurring in the implementation of a new application, as it can capture the functional requirements and the expected behavior of the system or the process, as well as the exceptions and alternative flows. A use case can also help to design and execute test cases that cover all the possible scenarios and outcomes. In this case, a use case could have prevented the problem of a worker using a field that was not supposed to be used, as it could have specified the valid inputs and outputs for the report, and the actions and responses of the system or the process. Prototyping, diagrams, and document analysis are other techniques that can help to analyze and communicate requirements, but they do not necessarily prevent problems from occurring in the implementation of a new application, as they do not describe the interactions and outcomes of the system or the process in detail. References: PMI Guide to Business Analysis, page 165-166.

Explanation
Version control is a technique that helps to manage changes to requirements and ensure that only authorized changes are made. It also helps to maintain a history of requirements changes, which records the date, reason, and impact of each change. Tracking the status of each requirement helps to monitor the progress and completion of requirements throughout the project life cycle. These practices help to ensure the integrity of requirements and avoid confusion, inconsistency, or ambiguity. References: = PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline (2019), page 8; Business Analysis for Practitioners: A Practice Guide (2015), page 38.