CBAP Exam Dumps - IIBA Certified Business Analysis Professional Questions and Answers

 A scribe is a participant who has to keep the minutes and details of the conversation during interviews. A scribe is a person who records the key points, questions, answers, and action items that are discussed during the interview. A scribe helps to capture the information accurately and completely, as well as to document any assumptions, issues, or risks that arise during the interview. A scribe also helps to prepare and distribute the interview notes and follow-up actions to the relevant stakeholders. A scribe can be a business analyst, a stakeholder, or a third-party facilitator, depending on the availability and suitability of the role. References: IIBA BABOK Guide v3, section 4.2.5.2, page 116; CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, page 178; Free CBAP CBAP® Exam Questions - IIBA CBAP Exam - Study4Exam, question 240.

 The medium is the component of the communication model that is responsible for transferring the message between two or more entities. The medium is the channel or the tool that is used to transmit the message from the sender to the receiver. The medium can be verbal, written, visual, or a combination of these. The medium can also be electronic, such as email, phone, or video conference, or physical, such as paper, board, or face-to-face meeting. The medium acts as a translator by converting the message into a form that can be understood by the receiver. The medium also influences the effectiveness and efficiency of the communication, as different mediums have different advantages and disadvantages, such as speed, cost, feedback, and noise. References: IIBA BABOK Guide v3, section 2.2.2.3, page 25; CBAP / CCBA Certified Business Analysis Study Guide, chapter 6, page 236; CBAP Business Analyst Exam Prep | Practice Quiz, question 256.

Ad images are a strong candidate to be addressed while planning for requirements reuse, because they are likely to change frequently and have common elements that can be reused across different weeks. Requirements reuse is a technique that involves identifying, storing, and reusing requirements or requirement components for future projects or initiatives. It can help to reduce duplication, improve consistency, and save time and effort. Ad images can benefit from requirements reuse, because they can use a standard template, format, and style, and only change the specific image and text for each new topping. Dough preparation, toppings preparation, and topping recipes are not good candidates for requirements reuse, because they are either stable or unique for each week. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Requirements Life Cycle Management, page 124

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 3: Requirements Life Cycle Management, section 3.7: Reuse Requirements, page 66

Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 3: Requirements Life Cycle Management, page 124

 Collaborative games are a technique that can be used to elicit requirements in a workshop setting. They involve engaging the participants in structured activities that encourage creativity, collaboration, and consensus. Collaborative games can help to avoid disrupting the workshop by creating a positive and productive atmosphere, reducing the potential for conflict, and increasing the buy-in and ownership of the requirements. Some examples of collaborative games are brainstorming, affinity diagramming, storyboarding, and prioritization games. References:

Business Analysis Body of Knowledge (BABOK) Guide, section 10.18, Collaborative Games

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, chapter 6, Elicitation and Collaboration, page 223-224

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, chapter 10, Review Questions, question 10.14, page 440

 A RACI chart is a matrix that defines the roles and responsibilities of the stakeholders involved in a task or a process. RACI stands for Responsible, Accountable, Consulted, and Informed. A RACI chart helps to clarify who is responsible for performing the work, who is accountable for the outcome, who needs to be consulted for input or feedback, and who needs to be informed of the progress or results. A RACI chart is important to ensure that the roles and responsibilities of the stakeholders are tracked and communicated, and that there is no confusion, duplication, or omission of tasks. References: [IIBA BABOK Guide v3], section 2.2.2.4, page 25; CBAP / CCBA Certified Business Analysis Study Guide, chapter 6, page 237; CBAP Sample Questions, question 235.

The BA should inform the stakeholders that the regulatory requirement takes precedence over other requirements, because it is a mandatory constraint that must be satisfied by the solution. The BA should explain the rationale and implications of the regulatory requirement, and how it affects the other requirements and the solution scope. The BA should also seek to resolve any conflicts or issues that may arise from the stakeholders, and ensure that they understand and accept the priority of the regulatory requirement. Measuring the value of the other requirements against the penalty of not meeting the regulatory requirement, comparing the regulatory requirement to the recommended solution, or determining a means to work around the regulatory requirement are not the best options, because they do not address the root cause of the problem and may result in non-compliance, legal liability, or stakeholder dissatisfaction. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Requirements Life Cycle Management, page 122

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 3: Requirements Life Cycle Management, section 3.5: Prioritize Requirements, page 62

Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 3: Requirements Life Cycle Management, page 122

A Gantt chart is a graphical tool that represents the duration of activities against a calendar. It shows the start and end dates, dependencies, and progress of each activity in a project. A Gantt chart can help project managers to plan, schedule, monitor, and control the project activities. It can also help to identify the critical path, which is the longest sequence of activities that determines the minimum time required to complete the project. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 47

What Is a Gantt Chart? | Definition & Examples | APM

Activity Duration Estimates: Definition, Importance and Techniques - Indeed, under What are activity duration estimates?

The risk management plan is a document that describes how risk management will be performed throughout the project. It includes tasks and roles for identifying, analyzing, responding, and monitoring risks. It also defines the risk categories, the schedules for risk management activities, the definitions of probability and impact, and the stakeholders’ tolerances for risk exposure and acceptance. The risk management plan provides guidance and direction for managing risks effectively and efficiently. References: CBAP / CCBA Certified Business Analysis Study Guide, chapter 5, page 228; CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, chapter 5, page 228.

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 waterfall software development life cycle is a methodology that divides the project into phases, and the project manager focuses on control of time, cost, and scope. The waterfall model is a linear and sequential approach that follows a predefined set of steps from the initiation to the closure of the project. The waterfall model assumes that the requirements, scope, and design of the project are clear and stable, and that each phase can be completed before moving to the next one. The waterfall model helps to ensure that the project deliverables meet the quality standards and specifications, and that the project is completed within the budget and schedule12. The spiral software development life cycle is a methodology that combines the iterative and incremental approach with the risk management and prototyping techniques. The spiral model is a cyclical and evolutionary approach that follows a series of loops or iterations from the planning to the deployment of the project. The spiral model assumes that the requirements, scope, and design of the project are dynamic and complex, and that each iteration can be refined and improved based on the feedback and learning from the previous ones. The spiral model helps to identify and mitigate the risks and uncertainties of the project, and to deliver a functional and adaptable product13. The agile software development life cycle is a methodology that emphasizes the collaboration, communication, and flexibility among the project stakeholders. The agile model is an adaptive and iterative approach that follows a series of short and frequent cycles or sprints from the conception to the delivery of the project. The agile model assumes that the requirements, scope, and design of the project are emergent and changing, and that each sprint can deliver a working and valuable product increment. The agile model helps to respond to the changes and feedback of the project, and to maximize the customer satisfaction and value14. The incremental software development life cycle is a methodology that breaks down the project into smaller and manageable chunks or modules. The incremental model is a progressive and modular approach that follows a series of steps from the analysis to the implementation of each module of the project. The incremental model assumes that the requirements, scope, and design of the project are partially known and defined, and that each module can be developed and delivered independently. The incremental model helps to reduce the complexity and risk of the project, and to provide a gradual and continuous delivery of the product15. References:

CBAP® Handbook

Waterfall Model - iiba.org

Spiral Model - iiba.org

Agile Model - iiba.org

Incremental Model - iiba.org