How to Easily Pass the IIBA CBAP Exam: Expert Advice

 Functional decomposition is the analysis of complex systems by breaking them down into smaller simpler elements. It involves breaking down processes, systems, functional areas, or deliverables into simpler components, so that each part can be analyzed separately12. By breaking down larger components into smaller parts, it allows the organization to measure and track each work effort involved in implementing the solution. It also helps in the assessment of the effectiveness of each sub-component as it relates to other larger or smaller components3. Functional decomposition is a technique used in business analysis to facilitate the understanding and management of large and complex processes2. It is also used in systems engineering, software architecture, database theory, machine learning, and a variety of other fields2. References: 1: Functional decomposition in business analysis – The Functional BA 2: Functional Decomposition: Definition, Diagrams, and Applications 3: 10.22 Functional Decomposition | IIBA®

Benchmarking is a business analysis approach that involves comparing one’s own performance, processes, or products with those of other organizations, especially the best performers or industry leaders, to identify gaps and opportunities for improvement. Benchmarking can help business analysts understand the competitive landscape, identify best practices, set realistic goals, and measure progress. In this question, Sally and her business analysis team are using benchmarking to determine what the competition is offering and how they can increase their revenue by remaining competitive. References:

• CBAP® Handbook, page 15, section 4.1.2.3
• BABOK® Guide, page 32, section 3.2.3
• CBAP / CCBA Certified Business Analysis Study Guide, page 96, section 3.2.3
• What is a Competitive Analysis — and How Do You Conduct One?

Prioritizing requirements by the likelihood of success is a technique that can help build confidence and trust among the project stakeholders, especially if the project is complex, risky, or has a long duration. By delivering some of the requirements that have a highchance of success early in the project, the business analyst can demonstrate the value of the project and the effectiveness of the business analysis process. This can also help reduce resistance to change and increase user satisfaction and adoption. Some of the other factors that can be used to prioritize requirements are business value, urgency, dependency, risk, cost, and effort. References:

• Certified Business Analysis Professional (CBAP) Handbook, page 6, section 4. Review the Exam Blueprint.
• BABOK Guide v3, page 34, section 4.2.3. Prioritize Requirements.

A RACI chart is a tool that helps to define and clarify the roles and responsibilities of different stakeholders in a project or a process. It stands for Responsible, Accountable, Consulted, and Informed, which are the four types of tasks or activities that stakeholders can be involved in. A RACI chart is a matrix that lists the tasks or activities in the left column and the stakeholders or roles in the top row. For each task or activity, the RACI chart indicates who is Responsible, Accountable, Consulted, or Informed by using the letters R, A, C, or I. A RACI chart can help to improve communication, collaboration, and accountability among stakeholders, and to avoid confusion, duplication, or conflict of roles. A RACI chart can be used as part of the stakeholder analysis process, which is the process of identifying, categorizing, and assessing the stakeholders of a project or a process, and understanding their needs, expectations, and interests.

References:

• RACI Chart - a how to guide to using RACI, paragraph 1
• How the RACI Matrix Streamlines Stakeholder Engagement, paragraph 1
• Stakeholder Wrangling 101: The RACI Framework, paragraph 1
• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 30, section 2.51

The conduct stakeholder analysis task is one of the tasks in the business analysis planning and monitoring knowledge area. According to the BABOK® Guide1, this task involves identifying and analyzing the stakeholders of a change, assessing their attitudes, expectations, influence, and interests regarding the change, and determining the best ways to engage and communicate with them. The purpose of this task is to ensure that the business analysis activities are aligned with the needs and concerns of the stakeholders, and that the stakeholders are appropriately involved and informed throughout the change.

The other options are not accurate descriptions of the conduct stakeholder analysis task, but rather:

• A. This is a partial description of the define business need task, which identifies the business problem or opportunity that requires analysis.
• C. This is a partial description of the assess capability gaps task, which compares the current and future states to identify the gaps that must be addressed by a solution.
• D. This is a vague and incomplete description of the conduct stakeholder analysis task, as it does not mention the analysis, assessment, and engagement aspects of the task.

References:

• CBAP® Handbook, page 15, section 4.1.2.3
• BABOK® Guide, page 32, section 3.2.3
• CBAP / CCBA Certified Business Analysis Study Guide, page 96, section 3.2.3
• How To Create a Stakeholder Analysis (With Example)
• How to Perform a Stakeholder Analysis | Lucidchart

 Brainstorming is a technique for generating creative ideas and solutions through intensive and freewheeling group discussion. One of the guidelines for effective brainstorming is to encourage quantity over quality, meaning that participants should try to generate as many ideas as possible without worrying about their feasibility or quality. Setting a limit of ten ideas may discourage further creativity and prevent the group from exploring other potential solutions. Therefore, the goal should be to come up with as many solutions as possible, not just ten ideas. References:

• BABOK® Guide, section 10.25.3, page 404
• Certified Business Analysis Professional™ (CBAP®) Handbook, page 6
• Tips for Earning a Business Analysis Certification | IIBA®

The requirements analysis processes are the activities that prioritize, organize, specify, model, verify, and validate the requirements for the solution. They ensure that analysis and implementation efforts focus on the most critical requirements that deliver the most value to the stakeholders and the organization. They also help to resolve any conflicts or inconsistencies among the requirements and the stakeholders. References:

• CBAP® Handbook, page 6, section 2.4 Review the Exam Blueprint
• BABOK® Guide, page 30, section 3.2 Requirements Analysis and Design Definition
• CBAP / CCBA Certified Business Analysis Study Guide, page 111, chapter 5 Requirements Analysis

 Risk Data Quality Assessment is a technique that evaluates the degree to which the data about individual project risks is useful for risk management. It involves examining the extent to which the risk data is accurate, reliable, timely, complete, and realistic. This helps to determine the quality and credibility of the information used for risk analysis and response planning. References:

• BABOK® Guide v3, section 11.6.5.8, page 417
• CBAP® Exam Prep Study Guide, chapter 9, page 339
• CBAP® Certification Study Guide v3.0, chapter 9, page 301

Mitigation is not a category of risk tolerance, but rather a strategy for reducing the probability or impact of a risk. Risk tolerance refers to the degree of uncertainty that a stakeholder is willing to accept in relation to the achievement of the project or solution objectives. According to the BABOK® Guide1, there are three categories of risk tolerance associated with the stakeholders: risk-averse, risk-neutral, and risk-seeking. These categories are based on how much risk the stakeholders can tolerate and how they perceive the potential rewards of taking risks.

• Risk-averse stakeholders prefer to avoid risks or minimize their exposure. They tend to choose safer options that have lower returns but higher certainty. They may require more analysis and evidence before making decisions or approving requirements.
• Risk-neutral stakeholders are indifferent to risks and rewards. They base their decisions on the expected value of the outcomes, regardless of the uncertainty involved. They may accept higher risks if they are compensated by higher returns, or lower risks if they are accompanied by lower returns.
• Risk-seeking stakeholders prefer to take risks or maximize their exposure. They tend to choose riskier options that have higher returns but lower certainty. They may be willing to accept lower levels of analysis and evidence before making decisions or approving requirements.

References:

• CBAP® Handbook, page 6, section 4. Review the Exam Blueprint, under Requirements Analysis and Design Definition, task 5.1: Prioritize Requirements
• BABOK® Guide, page 33, section 4.2.1: Prioritize Requirements
• Risk Tolerance - Overview, Factors, and Types of Tolerance
• Applying stakeholder risk tolerance strategies in business

Stakeholder analysis is performed as soon as a business need is identified, as this is the first step in the business analysis process. Stakeholder analysis helps to identify who are the people or groups that have an interest or influence in the project, what are their needs and expectations, and how to engage them effectively. Stakeholder analysis is essential for defining the project scope, objectives, requirements, risks, and success criteria. Stakeholder analysis is also an ongoing process that should be revisited throughout the project lifecycle, as stakeholders may change or new ones may emerge12. References:

• Stakeholder Analysis: Overview, Tools and Techniques - KnowledgeHut
• How to Perform a Stakeholder Analysis | Lucidchart