IIBA Updated CBAP Exam Questions and Answers by millicent

The lead BA is trying to improve the business analysis practices by finding out the root causes of the problems and inefficiencies in the current state. By measuring the time spent on planned and unplanned activities, the lead BA can identify the typical missing or wasteful activities that are affecting the quality and timeliness of the deliverables. For example, the lead BA may discover that the BAs are spending too much time on rework, clarifications, or scope changes due to poor elicitation, validation, or prioritization techniques. The lead BA can then propose solutions to address these issues and enhance the business analysis performance and value. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Planning and Monitoring, page 57

Senior Business Analysis Certification CBAP® | IIBA®, Business Analysis Planning and Monitoring, page 5

According to the BABOK Guide, “prioritization is the process of ranking requirements in order of importance or urgency”. However, not all requirements can be prioritized at the same time, especially if they are not stable or well-defined. In such cases, the BA should leave the priority unfilled until the requirements are clarified and agreed upon by the stakeholders. This will avoid premature decisions that may lead to rework, conflicts, or missed expectations. The BA should also communicate the rationale for leaving the priority unfilled and the criteria for assigning it later. References: BABOK Guide, Version 3, Section 6.2.4.3, CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8, Page 287

 The BA could have assessed the current state and stakeholder needs to prevent this situation. The current state is the description of the existing situation, including the problems, opportunities, capabilities, and constraints of the organization and its stakeholders. The stakeholder needs are the expectations, preferences, and requirements of the stakeholders that are relevant to the change initiative. By assessing the current state and stakeholder needs, the BA could have identified and documented the existing report “Consolidated Sales by Customer” as a requirement, and ensured that it was not affected or replaced by the new report “Customer Sales by Date”. The BA could have also verified and validated that the new report met the stakeholder needs and did not cause any negative impacts or trade-offs. The other options are not the best answers, as they are more related to the evaluation of the solution or the organization, rather than the identification and management of the requirements. References: CBAP Handbook, CBAP Study Guide, BABOK Guide

Interviews are a common and effective technique for eliciting requirements from stakeholders1234.

Interviews allow the BA to gain an in-depth understanding of the business needs and create the opportunity for a discussion and clarification on any statements made by the stakeholder5.

Interviews enable the BA to ask open-ended questions, probe for details, and uncover hidden or implicit requirements that the stakeholder may not be aware of or may not express otherwise124.

Interviews can also help the BA to establish rapport and trust with the stakeholder, which can facilitate the collaboration and communication throughout the project12.

Interviews can be used to verify facts, clarify ambiguity, trigger enthusiasm, engage end users, identify requirements and solicit opinions and ideas3.

The other options are not as good as option D because:

Option A is not a good approach because it assumes that the current solution is suitable for the PGA department without validating it with the actual users. Deploying the solution without eliciting user requirements may result in low user satisfaction, low adoption, and poor performance. Surveying users for improvement proposals after the deployment may be too late or too costly to implement changes.

Option B is better than option A, but it still relies on the assumption that the current solution can meet the PGA needs with minimal customization. Utilizing the solution in a test environment with actual data may help elicit some feedback, but it may not capture all the requirements or address all the issues that the users may have. Moreover, this approach may require more time and resources than conducting interviews.

Option C is also better than option A, but it may not be sufficient to collect the requirements from the sponsor and domain subject matter experts only. The sponsor may not represent the views and needs of all the users, and the domain subject matter experts may not be familiar with the current solution or the future state of the process. Collecting the requirements from a wider range of stakeholders, including the end users, can help ensure that the solution is aligned with the business goals and user expectations.