IIBA Updated CBAP Exam Questions and Answers by mckenzie

 Collaborative games are a technique that can be used to elicit requirements in a workshop setting. They involve engaging the participants in structured activities that encourage creativity, collaboration, and consensus. Collaborative games can help to avoid disrupting the workshop by creating a positive and productive atmosphere, reducing the potential for conflict, and increasing the buy-in and ownership of the requirements. Some examples of collaborative games are brainstorming, affinity diagramming, storyboarding, and prioritization games. References:

• Business Analysis Body of Knowledge (BABOK) Guide, section 10.18, Collaborative Games
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, chapter 6, Elicitation and Collaboration, page 223-224
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, chapter 10, Review Questions, question 10.14, page 440

 An unstructured interview is a type of elicitation that allows each stakeholder to freely discuss their role in a particular process. An unstructured interview is a flexible and informal conversation that does not follow a predefined set of questions or topics. An unstructured interview allows the interviewer to explore the stakeholder’s perspectives, opinions, needs, and expectations in depth. An unstructured interview also allows the interviewer to adapt to the stakeholder’s responses and follow new lines of inquiry. An unstructured interview is useful for eliciting tacit knowledge, complex information, and emotional aspects of the stakeholder’s role. References: IIBA BABOK Guide v3, section 4.2.5, page 115; CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, page 177; CBAP Sample Questions, question 238.

The possible reason why the solutions’ team was unable to accurately assess the merits of each of the proposed solutions is that the requirements and design options were not detailed enough. This means that the requirements and design options did not provide sufficient information, clarity, or specificity for the solutions’ team to understand, evaluate, and compare the different approaches for implementing the feature. The lack of detail may also lead to ambiguity, inconsistency, or incompleteness in the requirements and design options, which can affect the quality and feasibility of the solutions. The BA should ensure that the requirements and design options are detailed enough to meet the needs and expectations of the stakeholders, and to support the decision making and implementation processes. Requirements are not allocated to solution components, too many approaches are dividing the team, or business needs are unclear to the team are not the best options for the possible reason, because they are either irrelevant, inaccurate, or not the root cause of the problem. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 7: Requirements Analysis and Design Definition, page 280
• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 7: Requirements Analysis and Design Definition, section 7.5: Specify and Model Requirements, page 133
• Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 7: Requirements Analysis and Design Definition, page 280

The stakeholders and the BA need to measure benefits, penalties, and costs to determine if the solution is providing expected value and ensure the accuracy of the measurements. Benefits are the positive outcomes or value that the solution delivers to the stakeholders or the organization. Penalties are the negative consequences or costs that the solution may incur if it fails to meet the requirements or expectations. Costs are the resources or expenses that are required to implement, operate, and maintain the solution. By measuring benefits, penalties, and costs, the stakeholders and the BA can assess the return on investment (ROI), the net present value (NPV), and the break-even point (BEP) of the solution, and compare them with the expected or planned values. This can help to evaluate the effectiveness, efficiency, and feasibility of the solution, and to identify any gaps, issues, or opportunities for improvement. Strategy, solution, and scope are not the best options to measure, because they are either too general, too abstract, or not directly related to the value of the solution. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Solution Evaluation, page 337
• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 8: Solution Evaluation, section 8.2: Analyze Performance Measures, page 153
• Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 8: Solution Evaluation, page 337