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

A governance approach is a technique that helps to define and establish the roles, responsibilities, authorities, and decision-making processes for the business analysis work. A governance approach identifies the stakeholders who have the power and influence to approve, reject, or modify the requirements or the solution, and the criteria and mechanisms for obtaining their approval. A governance approach can help the BA to identify the stakeholder who can approve access to the database, as it can specify who owns the database, who has the authority to grant or deny access, and what are the steps and procedures to request and obtain access. A solution scope is a technique that helps to define the boundaries and context of the solution. A solution scope identifies the elements that are within the scope, the elements that are out of scope, and the interfaces and interactions between the elements. A solution scope can help the BA to clarify the objectives and requirements of the solution, but it does not identify the stakeholder who can approve access to the database. A requirements architecture is a technique that helps to organize and structure the requirements into a coherent and consistent framework. A requirements architecture defines the relationships, dependencies, and hierarchies among the requirements, and the level of detail and abstraction of each requirement. A requirements architecture can help the BA to manage the complexity and traceability of the requirements, but it does not identify the stakeholder who can approve access to the database. A change strategy is a technique that helps to plan and manage the changes to the requirements or the solution throughout the project lifecycle. A change strategy defines the roles and responsibilities, the criteria and procedures, the tools and techniques, and the documentation and communication for handling the changes. A change strategy can help the BA to ensure that the changes are properly identified, analyzed, approved, implemented, verified, and tracked, but it does not identify the stakeholder who can approve access to the database. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.14: Governance Approach, p. 516-517; Section 10.42: Scope Modeling, p. 554-556; Section 10.41: Requirements Architecture, p. 553-554; Section 10.11: Change Control Process, p. 510-512.

The stakeholders that were missed in the requirements are the end users. End users are the people who will use the solution or be affected by its outcomes. They are a key source of requirements, as they can provide valuable insights into the needs, expectations, preferences, and pain points of the solution. The BA should elicit requirements from the end users, as well as validate and verify them with their feedback. The BA should also ensure that the end users are involved throughout the project lifecycle, from planning to testing to implementation. The other options are not the stakeholders that were missed, as they are either not directly related to the solution or not the primary source of requirements. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Key Concepts, Section 2.3: Stakeholders, p. 59-60
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 2: Business Analysis Key Concepts, Section 2.3: Stakeholders, p. 28-29
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.1: Prepare for Elicitation, p. 97-98

The business analysis approach is the set of processes, activities, tasks, deliverables, and techniques that are used to conduct business analysis. The business analysis approach should be aligned with the needs, preferences, and expectations of the stakeholders, as well as the characteristics and constraints of the project and the organization. The level of formality is one of the factors that influences the business analysis approach. It refers to the degree of rigor, detail, and documentation that is required for the business analysis work. The level of formality may vary depending on the type, size, complexity, and risk of the project, as well as the regulatory and governance requirements, the stakeholder involvement, and the organizational culture. In this scenario, the BA is dealing with two main stakeholders that have different levels of formality. The government agency is highly regulated and may require a formal approach that follows strict standards, policies, and procedures, and produces detailed and comprehensive documentation. The private company is less formal and may prefer a flexible and collaborative approach that allows for rapid changes, feedback, and experimentation, and produces minimal and concise documentation. Therefore, the BA’s strategy should be to develop consensus on a tailored approach for formality that balances the needs and expectations of both stakeholders, and that is suitable for the project context and objectives. The BA should facilitate a meeting with the representatives from each entity and discuss the advantages and disadvantages of different levels of formality, and how they can be adapted and customized to meet the project requirements and deliver value. The BA should also consider the impact of the level of formality on the other aspects of the business analysis approach, such as the planning, elicitation, analysis, validation, and management of the requirements and design specifications. The BA should seek to achieve a common understanding and agreement among the stakeholders on the level of formality and the business analysis approach. Option B is incorrect because using a formal approach to appeal to the government entity’s higher authority may not satisfy the needs and preferences of the private company, and may create conflict and dissatisfaction among the stakeholders. Option C is incorrect because employing the standard business analysis level of formality may not be appropriate or effective for the project and the organization, and may not address the specific needs and expectations of the stakeholders. Option D is incorrect because asking the government entity to accept a flexible collaborative approach may not comply with the regulatory and governance requirements, and may create resistance and distrust among the stakeholders. References: BABOK Guide v3, Chapter 2: Business Analysis Planning and Monitoring, Section 2.2: Plan Business Analysis Approach, p. 28-32; Chapter 10: Techniques, Section 10.6: Business Analysis Approach, p. 501-502.

The BA is using this technique to manage stakeholder collaboration. This technique is known as affinity diagram, which is a technique that helps organize and categorize a large number of ideas, issues, or requirements into logical groups based on their natural relationships or common themes. Affinity diagram can help to manage stakeholder collaboration by facilitating brainstorming, encouraging participation, building consensus, and resolving conflicts among the stakeholders. Affinity diagram can also help to elicit, analyze, and prioritize requirements, but that is not the primary purpose of this technique. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, Section 4.3: Confirm Elicitation Results, p. 175-176
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.3: Confirm Elicitation Results, p. 108-109
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 9: Underlying Competencies, Section 9.3: Collaboration and Teamwork, p. 350-351

 The first step for the BA is to understand the current state of the service provider’s business operations and the root causes of the reduced profit margin. This will help the BA to identify the problems and opportunities for improvement, as well as to establish a baseline for measuring the effectiveness of the proposed solutions. The BA can use various techniques to conduct the current state analysis, such as document analysis, interviews, observation, surveys, and SWOT analysis. The other options are not the first step, as they are either focused on the future state or the solution, without understanding the current situation and the underlying needs. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 93-94
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 106-109

 In addition to existing regulations and contracts, the BA also checks the policies of the organization that may constrain the project. Policies are the guidelines or principles that govern the decision making and actions of the organization. They reflect the values, vision, and mission of the organization and provide a framework for achieving its goals and objectives. Policies can also influence the scope, feasibility, and acceptance of the project and its solution. Therefore, the BA should identify and analyze the policies that are relevant to the project and ensure that they are aligned with the requirements and the solution. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 206-207
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 106-107
• 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

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

 A communications management plan is a document that describes how the business analyst will communicate with the stakeholders throughout the project. It includes information such as the timing and frequency of communication, the location and mode of communication, the tools and techniques to be used, the delivery methods and formats, and the stakeholders’ preferences and needs. A communications management plan helps to ensure that the stakeholders are informed, engaged, and satisfied with the project progress and outcomes. A stakeholder collaboration plan is a document that describes how the business analyst will collaborate with the stakeholders to elicit, analyze, validate, and manage the requirements. A business analysis plan is a document that describes how the business analyst will conduct the business analysis activities, such as the scope, approach, deliverables, tasks, resources, and schedule. A stakeholder analysis plan is a document that describes how the business analyst will identify, analyze, and prioritize the stakeholders and their needs, expectations, and influence. References: BABOK Guide v3, Chapter 2: Business Analysis Planning and Monitoring, Section 2.5: Plan Business Analysis Communication, p. 38-40; Chapter 3: Business Analysis Governance and Information Management, Section 3.1: Plan Business Analysis Governance, p. 50-51.

 The BA should consider including the priority of each requirement in the project requirements document. The priority is the relative importance or urgency of a requirement in relation to other requirements, based on the value, risk, or dependency of the requirement. By assigning a priority to each requirement, the BA can ensure that the requirements are delivered according to the customer expectations and the project constraints, such as time, budget, and scope. The priority can also help to manage changes, resolve conflicts, and allocate resources for the requirements. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Requirements Analysis and Design Definition, Section 6.3: Prioritize Requirements, p. 255-256
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 6: Requirements Analysis and Design Definition, Section 6.3: Prioritize Requirements, p. 155-156