PDF CCBA Study Guide

The BA missed the element of understanding stakeholder roles, which is part of the task of identifying stakeholders in the business analysis planning and monitoring knowledge area. The BA should have identified the roles and responsibilities of the stakeholders, including who has the authority to approve the requirements, before eliciting, specifying, and modelling them. This would have avoided the delay and confusion caused by the wrong sign-off authority. The other options are not relevant to the question, as they are related to different tasks or knowledge areas. References: [A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide)], Chapter 3: Business Analysis Planning and Monitoring, Section 3.1: Plan Stakeholder Engagement, Task 3.1.1: Identify Stakeholders, Page 36. [Business Analysis for Practitioners: A Practice Guide], Chapter 2: Needs Assessment, Section 2.2: Identify Stakeholders, Page 23.

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

The BA should select CRUD (Create, Read, Update, and Delete) matrix as the technique that would be appropriate for determining how and who uses data across the identified processes. CRUD matrix is a table that shows the actions that different roles or stakeholders can perform on data entities or objects within a system or solution. CRUD matrix can help to define the data access rights and permissions for each role or stakeholder, as well as the data dependencies and interactions among processes.

The other options are incorrect because:

• Option A is incorrect because stakeholder list, map, or personas are not techniques for determining how and who uses data, but techniques for identifying and analyzing stakeholders. Stakeholder list, map, or personas are tools that provide information about the characteristics, needs, expectations, and influences of stakeholders. Stakeholders are individuals or groups who have an interest or stake in a change or solution.
• Option B is incorrect because data dictionary is not a technique for determining how and who uses data, but a technique for defining and describing data. Data dictionary is a repository that contains the definitions, attributes, formats, and relationships of data elements or objects within a system or solution. Data dictionary can help to standardize and document the data requirements and specifications for a solution.
• Option D is incorrect because decision model is not a technique for determining how and who uses data, but a technique for modeling and analyzing decisions. Decision model is a graphical representation of the logic, rules, criteria, and outcomes of decisions within a system or solution. Decision model can help to simplify and clarify the decision-making process and its impact on the solution.

References:

• BABOK Guide v3, section 10.16: CRUD Matrix
• CCBA Practice Test, question 5

According to the BABOK® Guide, a risk is an uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives. A business analyst (BA) should identify, analyze, and manage risks throughout the business analysis process. In this scenario, the potential organizational restructure is a risk that could affect the requirements and the solution scope of the new system. Therefore, the BA should record this risk and assess its probability and impact on the project objectives. The BA should also plan how to respond to this risk if it materializes, such as by revising the requirements or modifying the solution design. This way, the BA can proactively manage the risk and minimize its negative effects on the project. References:

• [BABOK® Guide], section 10.1: Risk Analysis and Management
• CCBA Exam Questions & Answers with Explanations, question 25