CBAP Exam Dumps - Certified Business Analysis Professional

 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.

According to the BABOK® Guide1, the business analysis approach is the set of processes, tools, deliverables, techniques, and standards that will be used to perform business analysis work on a project. The approach can be either plan-driven, adaptive, or a hybrid of both. A plan-driven approach is more suitable for projects that have stable and well-defined requirements, low levels of change, and clear acceptance criteria. An adaptive approach is more suitable for projects that have uncertain or evolving requirements, high levels of change, and emergent outcomes. Therefore, one of the factors that would drive the decision towards an adaptive approach is the organization’s tolerance for uncertainty, which means the degree to which the organization is willing to accept ambiguity and risk in the project. An organization with a high tolerance for uncertainty can benefit from an adaptive approach that allows for frequent feedback, experimentation, and learning. References:

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 57-59

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 89-91

The BA should not rely on a single source of data or a limited observation period to draw conclusions about the effectiveness of a system. The BA should conduct further analysis to ensure that the data is reliable, valid, and representative of the actual situation. The BA should also consider other factors that may affect the demand for the ticket booking service, such as seasonality, promotions, customer preferences, etc. The BA should use a variety of techniques, such as interviews, surveys, data mining, etc., to gather more information and confirm or refute the initial findings. References:

CBAP® Handbook, page 6, section 4. Review the Exam Blueprint

BABOK® Guide, page 35, section 3.2.2. Data Analysis

CBAP / CCBA Certified Business Analysis Study Guide, page 243, section 7.3.2. Data Analysis Techniques

The appropriate model type to assist the stakeholders in testing the performance and visual aspects of requirements 3 through 11 is a usability prototype. A usability prototype is a model that simulates the look and feel of the user interface of the solution, such as the layout, navigation, colors, fonts, and graphics. A usability prototype can help the stakeholders to evaluate the user experience, the ease of use, the accessibility, and the satisfaction of the solution. A usability prototype can also help to identify and resolve any usability issues or defects before the final implementation of the solution. 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. 265-266

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. 161-162

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 10: Solution Evaluation, Section 10.6: Validate Solution, p. 283-284

The BA presented an opportunity to increase efficiencies by simplifying the process of shipping to new countries and reducing the dependency on IT. By eliminating the need to maintain different variations of ship-to-country and location-to-route for various freight carriers, the BA enabled the business to save time and resources, and avoid potential errors or delays. This is an example of how a BA can add value to the business by identifying and proposing solutions that improve the current state and address the root causes of the problems. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Planning and Monitoring, page 50

Business Analysis Body of Knowledge (BABOK ®) Guide, Version 3, Chapter 6: Solution Evaluation, section 6.5.2: Assess Enterprise Limitations, page 176

Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 4: Business Analysis Planning and Monitoring, Week 2: Plan Business Analysis Approach, video: “Solution Evaluation”

 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

The BA should use the Allocate Requirements technique to assign requirements to the various solution components to ensure all objectives are met. This technique involves distributing stakeholder and solution requirements among solution components and releases in order to maximize the possible business value given the options and alternatives generated by the design team. The BA should consider the dependencies, constraints, priorities, and risks of each requirement and component, and ensure that the allocation is traceable, verifiable, and consistent with the project scope and objectives. References:

IIBA BABOK Guide, Section 7.2, Allocate Requirements

Oh Where, Oh Where Does This Requirement Belong? (BABOK 7.2), Bridging the Gap

Requirements Allocation, AcqNotes

The elicitation technique that the BA should select to enable the customer and the key stakeholders to visualize the final product is prototyping. Prototyping is a technique that involves creating a simplified or partial version of the solution that can demonstrate its features, functions, and appearance. Prototyping can help to elicit, validate, and verify the requirements, as well as to obtain feedback and approval from the stakeholders. Prototyping can also help to reduce the risks, costs, and time of the project by identifying and resolving any issues or gaps before the final implementation of the solution. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, Section 4.2: Conduct Elicitation, p. 167-168

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.2: Conduct Elicitation, p. 103-104

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. 161-162