Certification of Capability in Business Analysis CCBA Release Date

The BA should schedule a backlog walkthrough with the two stakeholders who do not agree on the priority of several product backlog items. This is because a backlog walkthrough is a technique that involves reviewing and discussing the product backlog items with the stakeholders to ensure a common understanding and agreement on their priority, scope, and acceptance criteria. A backlog walkthrough can help to resolve any conflicts or disagreements among the stakeholders and move the project forward. The other options are not as effective or appropriate as scheduling a backlog walkthrough. References:

BABOK Guide, section 10.24: Backlog Management

CCBA Practice Test, question 103

 An assumption is an influencing factor that is believed to be true but has not been confirmed to be accurate or that could be true now but may not be in the future1. The BA suggests identifying high customer demand by young families as an assumption because it is a factor that influences the business case and the solution design, but it is not based on any evidence or data. By identifying this assumption, the BA can manage the associated risks, such as the possibility of low customer demand, customer dissatisfaction, or market competition. The BA can also plan to validate or update this assumption as more information becomes available or as the market conditions change. The other options are not the main reasons for identifying assumptions, as they are either outcomes or activities that depend on the assumptions. References: [A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide)], Chapter 3: Business Analysis Planning and Monitoring, Section 3.4: Plan Business Analysis Approach, Task 3.4.2: Define Assumptions and Constraints, Page 49. [Business Analysis for Practitioners: A Practice Guide], Chapter 2: Needs Assessment, Section 2.3: Assess Current State of the Organization, Task 2.3.1: Identify and Analyze Assumptions, Page 29.

Explaining that the models are complementation to each other is a technique that helps to resolve the conflict by showing the benefits and limitations of each model, and how they can be used together to provide a more complete and accurate representation of the requirements1. Explaining that the models are complementation to each other can help the BA to satisfy both stakeholders, who may have different preferences or perspectives on how to describe the requirements. This technique can also enhance the quality and clarity of the requirements, as different models can capture different aspects or levels of detail of the requirements2. The other options are not appropriate techniques that the BA should use to resolve the conflict, as they may create or exacerbate issues, gaps, or inconsistencies in the requirements. Allowing both stakeholders to work on the models independently may result in duplication, contradiction, or misalignment of the requirements. Introducing a third model type may confuse or frustrate the stakeholders, who may not be familiar or comfortable with the new model. Suggesting a fusion model may not be feasible or effective, as different models may have different notations, semantics, or purposes. References:

1: How to Resolve Conflicts Between Stakeholders Over Requirements Models

2: Why Use Multiple Models to Describe Requirements?

Atomic is a characteristic of a quality requirement that means it cannot be broken down further into smaller requirements. It helps to ensure that the requirement is clear, concise, and complete. Owned, mapped, and allocated are not characteristics of a quality requirement, but rather attributes or relationships of a requirement. References: BABOK Guide v3, page 40; CCBA Mock Test, question 20