IIBA Updated CBAP Exam Questions and Answers by ozzie

Scenario and uses cases and user stories are conduct stakeholder analysis techniques that identify stakeholder roles that may serve as a useful starting point for identifying actors and roles. These techniques describe how stakeholders interact with the solution or the business process, and what their goals, needs, and expectations are. By creating scenarios and use cases and user stories, the business analyst can identify the primary and secondary stakeholders, as well as their roles and responsibilities. These techniques can also help to elicit, validate, and prioritize the requirements, as well as to communicate and collaborate with the stakeholders1234. References: 1: Scenarios, Use Cases, and User Stories1 2: Business Analysis Techniques: Eliciting Information and Collaborating with Stakeholders2 3: Use Cases and Scenarios3 4: User Stories4

 Root cause analysis is a technique that helps identify the underlying causes of failures or difficulties in accomplishing business analysis work. It involves asking a series of questions to determine the origin of a problem and the factors that contributed to it. By finding and addressing the root causes, the business analyst can prevent the problem from recurring and improve the performance of the business analysis process. References:

CBAP® Handbook, page 18, section 4.5. Manage Business Analysis Performance

BABOK® Guide, page 387, section 10.25. Root Cause Analysis

Tips for Earning a Business Analysis Certification, section 2. Understand the BABOK® Guide

 An assumption is a factor that is considered to be true, real, or certain without proof or demonstration. In this case, the vendor’s belief about the hardware delivery date is an assumption because it is not verified or guaranteed. The other options are not assumptions, but rather requirements, constraints, or criteria that the business solution must meet. References: CBAP / CCBA Certified Business Analysis Study Guide, Chapter 2: Business Analysis Planning and Monitoring, page 62. Certified Business Analysis Professional (CBAP®) Handbook, page 6.

The user stories approach for requirements organization is a technique that involves describing the stakeholders’ objectives, needs, and expectations in a concise and simple way. User stories are usually written in the format of “As a [role], I want [goal], so that [benefit]”. User stories help to capture the essence of what the stakeholders want from the solution, without going into too much detail or specifying a particular solution. User stories are useful for eliciting, prioritizing, and validating the requirements, as well as for communicating and collaborating with the stakeholders. User stories can also be used to create scenarios, use cases, and test cases1234. References: 1: User Stories | Examples and Template | Atlassian1 2: Chapter 15: Requirements and user stories - Agile Business2 3: Aligning User Stories, Use Cases and Requirements - Dice3 4: Writing User Stories for Requirements Gathering - Medium4