CBAP Exam Questions Tutorials

An Ishikawa diagram, also known as a fishbone diagram or a cause-and-effect diagram, is a graphical tool that shows the causes of a certain event. It is one of the seven basic tools of quality control and it is widely used in product design and quality defect prevention. A common use of this diagram is to identify potential factors causing an overall effect, such as a problem or a goal. It helps identify causal factors and contributing causes by organizing them 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 find the root causes and the most significant causes of the effect. References:

Ishikawa diagram - Wikipedia, paragraph 1

Cause and Effect Diagram (aka Ishikawa, Fishbone) - Six Sigma Study Guide, paragraph 1

Quality tool: Cause and effect diagram | CQI | IRCA, paragraph 1

The HAZOP technique, which stands for Hazard and Operability Study, is a qualitative technique that involves a disciplined analysis of the event sequences that could transform a potential hazard into an accident. The HAZOP technique is a systematic and structured method of identifying and evaluating the possible deviations from the intended design, operation, or functionality of a system, process, or product. The HAZOP technique uses a set of guide words, such as no, more, less, as well as, part of, and reverse, to generate different scenarios of what could go wrong and why. The HAZOP technique helps to identify the causes, consequences, and safeguards of the deviations, and to recommend the appropriate actions or controls to prevent or mitigate the hazards12. A failure mode and effects criticality analysis (FMECA) is a qualitative technique that involves an extension of the failure mode and effects analysis (FMEA) by adding a criticality rating to each failure mode. A FMECA is a method of identifying and evaluating the potential failures of a system, process, or product, and their impacts on the performance, safety, or reliability of the system, process, or product. A FMECA helps to prioritize the failures based on their severity and frequency, and to determine the corrective actions or preventive measures to reduce or eliminate the failures13. A failure mode and effects analysis (FMEA) is a qualitative technique that involves a systematic analysis of the potential failures of a system, process, or product, and their effects on the performance, safety, or reliability of the system, process, or product. An FMEA is a method of identifying and evaluating the causes, modes, and consequences of the failures, and the existing or planned controls to detect or prevent the failures. An FMEA helps to improve the design, operation, or functionality of the system, process, or product, and to reduce the risk of failures14. A preliminary risk analysis (PRA) is a qualitative technique that involves a high-level assessment of the risks that may affect a project or a solution. A PRA is a method of identifying and evaluating the sources, events, and impacts of the risks, and the existing or planned responses to the risks. A PRA helps to determine the feasibility and viability of the project or the solution, and to establish the scope and objectives of the risk management process15. References:

CBAP® Handbook

HAZOP Technique - iiba.org

Failure Mode and Effects Criticality Analysis - iiba.org

Failure Mode and Effects Analysis - iiba.org

Preliminary Risk Analysis - iiba.org

 Risk Analysis and Management is a technique that involves identifying, assessing, and treating the uncertainties and potential negative impacts that may affect the solution or the stakeholders. Risk Analysis and Management will enable the BA to record and handle the threats in the solution on an ongoing basis, because it can help the BA to quantify and prioritize the risks, determine the appropriate responses and mitigation strategies, and monitor and control the risk exposure and outcomes. Risk Analysis and Management can also help the BA to communicate and report the risk status and issues to the stakeholders and the organization, and to ensure that the solution delivers the expected value and benefits. Root Cause Analysis, Solution Performance Analysis, or Solution Scope are not the best options for recording and handling the threats in the solution on an ongoing basis, because they are either too specific, too general, or not directly related to the risk management process. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Solution Evaluation, page 346

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 8: Solution Evaluation, section 8.4: Assess Solution Limitations, page 158

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 8: Solution Evaluation, page 346

The BA should set up additional activities to collaboratively resolve the variations in the elicitation results, as this will help to ensure that the information is accurate, consistent, and complete. The BA can use techniques such as reviews, workshops, or focus groups to confirm the elicitation results with the stakeholders, identify and address any gaps, conflicts, or ambiguities, and reach a consensus on the requirements12. The other options are not effective ways to resolve the variations. Identifying a few key stakeholders to resolve the conflicts may exclude other relevant stakeholders and create bias or resentment. Removing requirements that cause differences may result in losing important information or value. Weighting the results from the observation because it is more reliable may ignore other sources of information or perspectives.