CBAP Exam Dumps - Certified Business Analysis Professional

The business process model is also known as the activity model. It is a graphical representation that captures all of the activities within a business, the inputs and outputs of each activity, and the required resources to complete each activity. It shows the sequence, dependencies, roles, and responsibilities of the activities, as well as the information and materials that flow between them. A business process model can help to document, analyze, improve, and automate the business processes that deliver value to the customers and stakeholders. A business process model can also help to align the business and IT strategies, and to identify the gaps and opportunities for innovation. References:

• Business Process Modeling: Definition, Benefits, and Examples - Kissflow, paragraph 1
• Business process modeling - Wikipedia, paragraph 1
• The business process model is also known as - VCEguide.com, answer B

Risk analysis is the process of defining and analyzing the dangers to individuals, businesses, and government agencies posed by potential natural and human-caused adverse events. Risk analysis involves identifying the sources and consequences of risk, estimating the likelihood and severity of risk events, and evaluating the effectiveness and feasibility of risk mitigation strategies. Risk analysis can be applied to various domains, such as IT, finance, security, health, environment, etc. Risk analysis can help to make informed decisions, optimize resource allocation, and enhance performance and resilience. References:

• Risk Analysis- Open Courses by Atlantic International University - AIU, paragraph 1
• Exam 1: Risk Analysis Flashcards | Quizlet, term 1
• What is risk analysis? Definition and meaning - Market Business News, paragraph 1

 A fishbone diagram, also known as an Ishikawa diagram or a cause-and-effect diagram, is a tool that can be used in root cause analysis. It helps to identify, explore, and display the possible causes of a specific problem or quality issue. A fishbone diagram has a main branch that represents the problem, and several sub-branches that represent the categories of causes. Each category can have further sub-causes that are linked to the main causes. The diagram resembles the skeleton of a fish, hence the name. A fishbone diagram can help to organize and analyze the causes of a problem, and to find the root cause that needs to be addressed. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 47
• Root Cause Analysis: Definition, Examples & Methods | Tableau, under Approaches to Root Cause Analysis
• What is Root Cause Analysis (RCA)? | ASQ, under Approaches to Root Cause Analysis

 The BA should proceed by obtaining approval to change the policies that are either constraining or insufficient to achieve the value desired by the future state. This is because the BA’s role is to align the solution with the business need and ensure that it delivers value to the stakeholders. If the existing policies are preventing or limiting the value realization, the BA should seek to change them by following the appropriate governance process and obtaining the necessary buy-in from the policy owners and other affected parties. Modifying the solution to comply with the policies, identifying an assumption about future state value, or modeling two future states are not the best options because they do not address the root cause of the problem and may result in suboptimal or ineffective solutions. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Strategy Analysis, page 254
• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 5: Strategy Analysis, section 5.3: Define Future State, page 99
• 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 6: Strategy Analysis, page 254

 A proven and tailored analysis approach is suitable for this project because it allows the business analyst to adapt to the specific needs and context of the project, while leveraging the best practices and standards of the profession. A proven and tailored analysis approach can also accommodate the different cultures, languages, regulations, and time zones of the countries involved in the project. A proven and tailored analysis approach is based on the following principles1:

• Business analysis is performed in alignment with the organization’s strategy and objectives
• Business analysis is driven by stakeholder needs and values
• Business analysis is collaborative and iterative
• Business analysis is adaptive and responsive to change
• Business analysis is supported by effective communication and documentation
• Business analysis is guided by ethical and professional conduct

References:

• 1: CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 1: Introduction to Business Analysis, page 82
• 2: CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition

A cause-and-effect diagram, also known as an Ishikawa diagram or a fishbone diagram, is a graphical tool that visualizes the result of a root cause analysis study. It helps to identify, sort, and display the possible causes of a specific problem or quality issue. It can also be used to explore the root causes of a problem or a desired outcome. The diagram looks like the skeleton of a fish, hence the name fishbone diagram. The effect or problem is shown as the fish’s head, and the causes are shown as the bones along the spine. The diagram helps to organize the causes into categories, such as people, processes, equipment, materials, environment, etc. The diagram can be created by brainstorming the causes and grouping them into major categories. The diagram can then be analyzed to identify the most likely or significant causes of the problem or outcome. References:

• Root Cause Analysis: Definition, Examples & Methods | Tableau, under Approaches to Root Cause Analysis
• Root Cause Analysis, Ishikawa Diagrams and the 5 Whys - isixsigma.com, paragraph 1
• Root Cause Analysis - Practical Action, paragraph 1

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