CCBA Exam Dumps - Certification of Capability in Business Analysis (CCBA)

 A structured walkthrough is a process of reporting, verifying, and validating requirements with the involved stakeholders. The purpose of a structured walkthrough is to ensure that the requirements are clear, complete, consistent, and aligned with the business needs and objectives. The first step of a structured walkthrough is to identify the objectives and goals of the session, such as what requirements will be reviewed, what feedback is expected, and what outcomes are desired. This helps to set the expectations and scope of the walkthrough and to focus the discussion on the relevant topics. References:

• Capability in Business Analysisâ„¢ (CCBA®) Certification, International Institute of Business Analysis (IIBA), 2020, p. 27.
• Structured Walkthrough Sessions: Why Bother?, Business Analyst Learnings, 2017.

 Brainstorming is an elicitation technique that involves generating a large number of ideas or options for solutions in a creative and collaborative way. Brainstorming is suitable for eliciting requirements from a large group of stakeholders, as it allows them to share their perspectives, opinions, and suggestions without any judgment or criticism. Brainstorming also helps to produce a broad set of options for solutions, as it encourages the participants to think outside the box and to build on each other’s ideas. Brainstorming can be done in various formats, such as face-to-face, online, or hybrid, and can be facilitated by a business analyst or a neutral moderator. The other options are not elicitation techniques that can achieve the same goal as brainstorming. Business rules analysis is a technique for identifying, documenting, and validating the rules that govern the behavior and operation of a business or a system. Benchmarking is a technique for comparing the performance, processes, or practices of an organization or a system with those of other organizations or systems that are considered to be the best in the industry or the domain. Data flow diagrams are a technique for modeling the movement and transformation of data within a system or a process. References:

• 9 Elicitation Techniques Used by Business Analysts – Tips and Guidance
• CBAP/CCBA preparation questions - The Functional BA
• Business Analysis: The Elicitation Process - UniversalClass
• Elicitation techniques in business analysis - PMWorld 360 Magazine

 According to the CCBA® Handbook, one of the tasks of the business analyst is to “assess proposed solution” (p. 12). This task involves evaluating the potential value and benefits of each solution option, comparing them to the costs and risks, and recommending the best option or no option at all. The inputs to this task are solution options, requirements, and risk assessments. The other options are not correct because:

• A. Solution options are an input to the assess proposed solution task, as they are the possible ways to address the business need and meet the requirements (p. 12).
• B. Requirements are an input to the assess proposed solution task, as they are the capabilities and conditions that the solution must have and meet to address the business need (p. 12).
• C. Risk assessments are an input to the assess proposed solution task, as they are the analysis of the uncertainties and potential negative impacts of each solution option (p. 12). References:
• CCBA® Handbook, p. 12
• BABOK® Guide, p. 106

Time boxing/budgeting is a technique for delivering prioritized requirements based on the work the project team can deliver within a set period. It is typically used on Agile Projects characterized by fixed deadlines and solutions that require frequent enhancements. With this technique, the project team can guarantee the delivery of the most important requirements on specific dates, with other requirements scheduled for release on successive dates. References:

• What Is Timeboxing? — Business Analyst Learnings
• Prioritization techniques in business analysis - The Functional BA

A solution approach is an output of the enterprise analysis tasks. A solution approach is a description of the strategy for delivering a solution that meets the business need and aligns with the enterprise architecture. A solution approach defines the scope, boundaries, assumptions, constraints, and risks of the solution, as well as the high-level requirements, costs, benefits, and feasibility of the solution. A solution approach is different from stakeholder concerns, which are the issues, problems, or interests that the stakeholders have in relation to the business need or the solution; solution performance assessment, which is the evaluation of how well the solution meets the business objectives and delivers the expected value; and assumptions and constraints, which are the influencing factors that affect the business analysis work or the solution. References:

• CCBA Handbook, page 10
• [BABOK Guide], page 10
• [Business Analysis for Practitioners: A Practice Guide], page 14
• [Business Analysis: The Question and Answer Book], page 9

Functional decomposition is a technique that breaks down a complex system or process into smaller and simpler components or activities. It helps to define scope by identifying the functions that are performed by or within a system or process. Decision modelling, SWOT analysis, and mind mapping are not techniques for defining scope based on business processes and activities. References: BABOK Guide v3, page 97; CCBA Mock Test, question 15

 Consulted is a RACI designation that indicates the stakeholders who need to be consulted before a decision or action is taken1. Consulted can help the BA to improve the communication of the business analysis information from the elicitation phase by involving the testing and training teams in the review and validation of the requirements and designs. By consulting the testing and training teams, the BA can ensure that the requirements and designs are feasible, testable, and aligned with the business needs and objectives2. The other options are not the best RACI designations for the training and testing teams, as they may not reflect their roles and responsibilities in the project. Responsible is a RACI designation that indicates the stakeholders who are assigned to do the work or complete the task3. Accountable is a RACI designation that indicates the stakeholders who have the authority and accountability for the work or task, and who approve the final outcome4. Informed is a RACI designation that indicates the stakeholders who need to be kept informed of the progress or results of the work or task. References:

• 1: RACI Matrix: Definition, Benefits and Examples
• 2: How to Consult Stakeholders Effectively
• 3: RACI Matrix: Definition, Benefits and Examples
• 4: RACI Matrix: Definition, Benefits and Examples
• : RACI Matrix: Definition, Benefits and Examples

The communication method was inappropriate because the BA sent a 600-page document without any summary or explanation to all stakeholders, which is likely to overwhelm and confuse them. The BA should have chosen a more suitable format and level of detail to communicate the status of the requirements management process, such as a dashboard or a report. The business rules, the distribution, and the models were not the main issues in this situation. References: BABOK Guide v3, page 50; CCBA Mock Test, question 17