How to Easily Pass the IIBA CBAP Exam: Expert Advice

Decision analysis is a technique that helps the BA evaluate and compare different alternatives based on their costs, benefits, and risks, and select the best option that meets the objectives and criteria. In this case, the BA needs to determine if one of the systems (Sys A or Sys B) is better suited to be modified and upgraded, based on the upgrade cost and cost new of each feature. The BA can use the table in the image to calculate the total cost of upgrading or creating new features for each system, and compare them with the expected value and return on investment of each system. The BA can also consider other factors, such as the feasibility, compatibility, reliability, and maintainability of each system, and the preferences and expectations of the stakeholders. By using decision analysis, the BA can make an informed and rational choice that maximizes the value and minimizes the risk of the solution. References:

• IIBA BABOK Guide, Section 10.23, Decision Analysis
• Decision Analysis for the Professional, SmartOrg
• Decision Analysis: Making Justifiable, Defensible Decisions, MindTools

The contract terms may affect the timing of the business analysis activities, as they may specify the deadlines, deliverables, and milestones that the BA must adhere to. The contract terms may also influence the business analysis approach, the level of detail and formality of the deliverables, and the stakeholder involvement. The other options are not directly related to the timing of the business analysis activities, although they may have some influence on the scope, quality, and complexity of the work. References:

• Business analysis approach planning – The Functional BA, paragraph 5
• Introduction & Guidance To Business Analysis Planning and Monitoring, section “Plan Business Analysis Approach”, paragraph 4
• Planning the Analysis Phase: using a Work Breakdown … - Modern Analyst, paragraph 1

 A business analysis checklist is a technique that helps to ensure that all the required business analysis activities and deliverables are completed and verified. A business analysis checklist can include items such as the scope statement, the stakeholder list, the requirements documentation, the traceability matrix, the validation criteria, the change requests, and the approval signatures. A business analysis checklist can help to mitigate the concern of the project board by providing a clear and comprehensive overview of the business analysis work and its quality. A data model is a technique that helps to represent the data and information needs of an organization or a solution using graphical or textual symbols and relationships. A data model can help to define and analyze the data requirements, but it does not ensure that all the requirements are verified. A use case diagram is a technique that helps to depict the interactions between a system and its actors using graphical symbols and relationships. A use case diagram can help to define and analyze the functional requirements, but it does not ensure that all the requirements are verified. A risk register is a technique that helps to identify, analyze, and manage the uncertainties and threats that may affect the project or the solution. A risk register can help to mitigate the potential impacts of the risks, but it does not ensure that all the requirements are verified. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.8: Business Analysis Checklist, p. 504-505; Section 10.18: Data Modelling, p. 522-524; Section 10.50: Use Case Diagram, p. 564-566; Section 10.51: Risk Analysis and Management, p. 567-569.

 A business process model is a graphical representation of the activities, flows, events, and decisions that make up a business process. It can help to describe the current and future states of the process, identify the inputs, outputs, roles, and resources involved, and analyze the performance, value, and quality of the process. A business process model is a useful requirements viewpoint for presenting the requirements for an auto insurance product to domain and implementation SMEs, as it can show how the product will support the business goals, meet the customer needs, and integrate with the existing systems and processes. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model and Validate Requirements, p. 263-264
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model Requirements, p. 159-160

When assessing the impact of safety concerns, the BA should consider the cost/benefit analysis of making the changes. This technique involves comparing the costs and benefits of different options to determine the optimal solution that maximizes the value and minimizes the negative consequences. The BA should consider the costs and benefits of the changes from various perspectives, such as financial, operational, social, environmental, and ethical. The BA should also consider the trade-offs and opportunity costs of the changes, as well as the risks and uncertainties involved. The cost/benefit analysis can help the BA to prioritize the changes, communicate the rationale, and justify the recommendations. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 7: Solution Evaluation, Section 7.3: Assess Proposed Solution, p. 315-316
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 10: Solution Evaluation, Section 10.3: Assess Enterprise Limitations, p. 277-278
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 10: Solution Evaluation, Section 10.4: Recommend Actions to Increase Solution Value, p. 279-280

 A workshop is a technique that helps to facilitate a structured and collaborative discussion among a group of stakeholders on a specific topic, such as the impact of the requirement changes. A workshop can help the BA to obtain a resolution on the impact of the requirement changes by providing an opportunity for the stakeholders to share their views, concerns, and suggestions, to analyze the pros and cons of the changes, to negotiate and resolve any conflicts or disagreements, and to reach a consensus on the best course of action. A workshop can also help the BA to communicate the rationale and benefits of the changes, to obtain feedback and approval from the stakeholders, and to document the outcomes and action items of the discussion. A focus group is a technique that helps to elicit the opinions, preferences, and feedback of a group of stakeholders about a specific topic, such as a prototype or a solution option. A focus group can help the BA to understand the stakeholders’ perception, ideas, and attitudes, and to identify any issues, gaps, or improvements, but it does not help the BA to obtain a resolution on the impact of the requirement changes. An interview is a technique that helps to elicit information from an individual stakeholder or a small group of stakeholders by asking open-ended, closed-ended, or probing questions. An interview can help the BA to gather detailed and specific information, to clarify and validate the requirements, and to build rapport and trust with the stakeholders, but it does not help the BA to obtain a resolution on the impact of the requirement changes. A survey is a technique that helps to collect quantitative or qualitative data from a large number of stakeholders by using a predefined set of questions or statements. A survey can help the BA to measure the level of satisfaction, agreement, or importance of the stakeholders, to identify the trends and patterns of the data, and to support decision making and prioritization, but it does not help the BA to obtain a resolution on the impact of the requirement changes. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.53: Workshops, p. 570-572; Section 10.24: Focus Groups, p. 532-533; Section 10.25: Interviews, p. 534-536; Section 10.46: Surveys or Questionnaires, p. 560-562.

 The requirement ‘’Ability to view policies created in the legacy system for a period of 6 months’’ is a transition requirement. A transition requirement is a temporary requirement that specifies the capabilities or conditions that the solution must have or meet during the transition from the current state to the future state. Transition requirements are typically related to data conversion, training, migration, or decommissioning. In this case, the requirement is needed to ensure that the policies created in the legacy system are still accessible for a limited time after the system is decommissioned, until the new system is fully operational and stable. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Key Concepts, Section 2.4: Requirements Classification Schema, p. 66-67
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 2: Business Analysis Key Concepts, Section 2.4: Requirements Classification Schema, p. 34-35

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. References: 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.

 A risk-averse organization is one that prefers to minimize or eliminate the exposure to risks, even if it means sacrificing some potential benefits or opportunities. A risk avoidance strategy is one that involves changing the project plan, scope, schedule, or budget to avoid the risk or its impact. A risk avoidance strategy is suitable for a risk-averse organization, as it reduces the uncertainty and the potential negative consequences of the risk. In this scenario, the BA has identified an assumption that has a high degree of uncertainty and may affect the validity of the requirements. The BA has added the assumption to the risk register and performed a risk analysis to handle this situation. If the organization is risk-averse, the BA may use a risk avoidance strategy to modify the requirements or the solution design to eliminate the dependency on the assumption, or to seek more information or evidence to validate the assumption. A risk acceptance strategy is one that involves acknowledging the risk and its impact, but not taking any action to prevent or reduce it. A risk acceptance strategy is suitable for a risk-seeking or risk-neutral organization, or for risks that have low probability or impact. A risk transfer strategy is one that involves shifting the responsibility or ownership of the risk or its impact to a third party, such as a vendor, a partner, or an insurer. A risk transfer strategy is suitable for risks that have high impact but low probability, or for risks that require specialized skills or resources to manage. A risk mitigation strategy is one that involves taking actions to reduce the probability or impact of the risk, such as implementing contingency plans, preventive measures, or backup solutions. A risk mitigation strategy is suitable for risks that have high probability and impact, or for risks that can be controlled or influenced by the project team. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.51: Risk Analysis and Management, p. 567-569; Free CBAP IIBA Actual Exam Questions & Answers, Question 467.

A stakeholder engagement approach is a plan that describes how the BA will interact with the stakeholders, identify their needs and expectations, and address their concerns and issues. A stakeholder engagement approach can help the BA avoid disagreements and conflicts by ensuring that the stakeholders are involved and informed throughout the business analysis process, and that their feedback and input are considered and incorporated. A stakeholder engagement approach can also help the BA build trust and rapport with the stakeholders, and manage their expectations and influence levels. By following a stakeholder engagement approach, the BA can ensure that the business analysis approach and the budget estimates are aligned with the stakeholder needs and agreed upon by all the relevant parties. References:

• IIBA BABOK Guide, Section 3.2, Plan Stakeholder Engagement
• Five-Step Approach to Stakeholder Engagement, BSR
• 5 steps to creating a stakeholder engagement plan (with template), Asana