CBAP Exam Questions & Answers

A collaborative approach is a type of elicitation approach that involves working with multiple stakeholders simultaneously to elicit, analyze, and validate requirements. A collaborative approach can help to complete requirements elicitation activities in a short period of time, as it can:

Reduce the number of individual meetings and interviews that need to be conducted

Increase the quality and quantity of information that can be gathered from different perspectives and sources

Enhance the communication and understanding among the stakeholders and the BA

Promote the consensus and agreement on the requirements and the solution scope

Identify and resolve any conflicts, issues, or gaps in the requirements

Some examples of collaborative elicitation techniques are:

Requirements workshops: A structured and facilitated session that brings together a group of stakeholders to elicit, analyze, and prioritize requirements

Brainstorming: A technique that generates a large number of ideas or solutions from a group of stakeholders in a creative and spontaneous manner

Focus groups: A technique that collects the opinions, preferences, and feedback of a group of stakeholders on a specific topic or issue

Prototyping: A technique that creates a simplified or partial version of the solution to elicit, demonstrate, and validate requirements

The other options are not correct because they are not types of elicitation approaches, but rather techniques that can be used within an elicitation approach. An experiment is a technique that tests a hypothesis or an assumption by observing the results of a controlled or simulated scenario. An estimation is a technique that approximates the size, cost, duration, or effort of a project or a solution. A research is a technique that collects and analyzes information from existing sources, such as documents, reports, databases, etc.

[BABOK Guide v3], Section 4.2: Conduct Elicitation, p. 100-101

Types of Elicitation Techniques for the Business Analyst, Blog Post, September 2018

Elicitation Techniques Used by Business Analysts -- Tips and Guidance, Blog Post, July 2023

Decision analysis is a technique for identifying and evaluating the possible options for a given problem or situation.It involves defining the criteria, alternatives, and consequences of each option, and applying a decision-making method to select the best option12. Decision analysis can be used for assessing and recommending solutions that fit an organization's need for a new third-party sales tool, as it can help to compare the features, benefits, costs, and risks of different vendors or products. The other options are not techniques for identifying suitable options, but rather tools or methods for other purposes.A balanced scorecard is a tool for measuring and managing the performance of an organization or a solution3.A vendor assessment is a method for evaluating the capabilities and suitability of a potential vendor or supplier4.A process analysis is a technique for understanding and improving the current or future state of a business process

The BA should recommend implementing a system that coordinates order processing activities in advance with all trips. This approach aims to ensure that orders are ready for loading when the trucks arrive, eliminating the waste of both the truck's and driver's time. By aligning order preparation with delivery schedules, the distributor can optimize resource utilization and improve efficiency.Reference: I need to search for specific references from Business Analysis Professional (CBAP) Learning documents or resources to provide an exact source.

Problem tracking is a document elicitation technique that can help in this scenario. Problem tracking is the process of identifying, documenting, and resolving issues that arise during the business analysis process. Problem tracking helps to ensure the quality and validity of the requirements and the solutions. Problem tracking also provides an opportunity for stakeholders to rank the importance of issues affecting them. Problem tracking can be done using various tools, such as spreadsheets, databases, or software applications. Problem tracking can help the business analyst to monitor the status of the issues, communicate the progress and outcomes to the stakeholders, and improve the business analysis performance and practices. The other options are not document elicitation techniques, but rather information elicitation techniques. Brainstorming is a technique that involves generating new ideas and finding solutions for a specific problem. Observation is a technique that involves watching how people perform their tasks or interact with a system. Interviews are a technique that involves asking questions and documenting the responses from a single person or a group of people.Reference:

Problem/Issue Tracking Technique --- Business Analyst Learnings, paragraph 1

Elicitation Methods | SpringerLink, paragraph 1

Understanding the Document Analysis Technique - Business Analyst Learnings, paragraph 1

This question is based on a case study that compares four scenarios for implementing a new system for a bank. The case study provides the following information about the duration of each scenario:

Scenario 1: 6 months

Scenario 2: 9 months

Scenario 3: 10 months

Scenario 4: 7 months

The question asks for the time difference in days between the shortest and longest implementation. The shortest implementation is Scenario 1, which is 6 months or 180 days. The longest implementation is Scenario 3, which is 10 months or 300 days.Therefore, the time difference in days is 300 - 180 = 120 days.Reference: The case study is available in the CBAP Exam Sample Questions and Exam Blueprint document1.The answer is also verified by the CBAP Exam Answer Key document2.Both documents are accessible from the IIBA website3.