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

A sponsor is a stakeholder who has the authority and responsibility to initiate, approve, support, and fund a project or a solution that will address a business need. A sponsor is also the primary decision maker and the ultimate owner of the project or the solution. A sponsor can help to define the business need, the solution scope, and the business case, as well as to authorize the actions needed to meet the identified business need. Robert needs to identify the sponsor as the stakeholder who will be responsible for authorizing the actions needed in order to meet the identified business need. References: BABOK Guide v3, page 50; CBAP / CCBA Certified Business Analysis Study Guide, page 158.

A horizontal prototype is a type of prototype that focuses on the user interface and the look and feel of the system, without much attention to the functionality or the back-end processes. It is useful for demonstrating the appearance and navigation of the system to the customer and getting feedback on the design. A horizontal prototype is also called a mock-up prototype or a storyboard prototype.

References:

Certified Business Analysis Professional Handbook, page 19

Certified Business Analysis Professional Specialization, Course 4, Week 3, Lesson 3.1

CBAP / CCBA Certified Business Analysis Study Guide, page 261

The timing of business analysis work is the most impacted element by the organization’s change from a waterfall methodology to an agile approach. This is because the waterfall and agile methods have different ways of planning, executing, and delivering business analysis work.

In a waterfall method, the business analysis work is done in a sequential and linear manner, following predefined phases and milestones. The requirements are elicited, analyzed, and documented upfront, before the design and development stages. The changes to the requirements are minimized and controlled, and the deliverables are verified and validated at the end of the project. The timing of business analysis work is fixed and predictable, but it may also be rigid and inflexible.

In an agile method, the business analysis work is done in an iterative and incremental manner, following short cycles of development and feedback. The requirements are elicited, analyzed, and documented continuously, along with the design and development stages. The changes to the requirements are welcomed and managed, and the deliverables are verified and validated throughout the project. The timing of business analysis work is variable and adaptable, but it may also be challenging and uncertain.

Therefore, the business analyst (BA) needs to adjust the timing of business analysis work according to the agile method, which involves:

Breaking down the requirements into smaller and manageable chunks, called user stories or features, that can be delivered in each iteration or sprint

Prioritizing and refining the requirements backlog, which is the list of all the requirements that need to be addressed in the project, based on the business value and stakeholder feedback

Collaborating and communicating with the project team and stakeholders frequently and effectively, using various techniques and tools, such as daily stand-ups, retrospectives, demos, etc.

Adapting and responding to the changing requirements and business needs, using various techniques and tools, such as change requests, impact analysis, traceability, etc.

References:

[BABOK Guide v3], Section 2.4: Plan Business Analysis Work, p. 24-27

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Planning and Monitoring, p. 43-44

Certified Business Analysis Professional™ (CBAP®) Specialization, Course 1: Business Analysis: Planning and Monitoring, Week 1: Introduction to Business Analysis Planning and Monitoring, Video: Waterfall vs. Agile

Agile vs. Waterfall | Pros, Cons, and Key Differences - ProductPlan

The conduct elicitation activity is a technique to understand stakeholder needs and identify potential solutions that may meet those needs. It involves guiding stakeholders and collaborating with them through the elicitation activity, doing research or running experiments, and capturing elicitation outcomes1. The captured outcomes should be recorded in a format that is clear, consistent, and accessible for future reference and analysis. Text messages sent via a secured mobile phone are not an acceptable element for requirements documentation, as they are not easily retrievable, traceable, or verifiable. Written documents, visual or audio recordings, and whiteboards are acceptable elements for requirements documentation, as long as they are properly stored, labeled, and managed2. References: Conduct Elicitation - iiba.org, Conducting elicitation activity – The Functional BA

A model is a simplified representation of a complex reality that is useful for understanding that reality and making decisions regarding it. A model can describe a situation or problem, define boundaries for the business domain, describe thought processes and action flows, and other aspects of the requirements. However, a model cannot define the resources that will be needed on the project team, as this is not part of the requirements but rather part of the project management plan. References: BABOK Guide v3, page 123; CBAP/CCBA Study Guide, page 181.

A regulator is a stakeholder who may be responsible to dictate that a specific process or technique be followed during the requirements elicitation activities. A regulator is an external stakeholder who has the authority to enforce laws, rules, standards, or policies that affect the project or the solution. A regulator may impose certain requirements or constraints on the project or the solution, such as compliance, security, privacy, or quality. A regulator may also require the use of specific methods, tools, or documentation for eliciting, analyzing, or validating the requirements. The other options are not necessarily responsible for dictating the process or technique for requirements elicitation, although they may have some influence or preference. A project manager is a stakeholder who is responsible for planning, executing, monitoring, and controlling the project activities and resources. A project manager may collaborate with the business analyst to select the appropriate process or technique for requirements elicitation, but does not have the authority to dictate it. A functional management is a stakeholder who is responsible for the day-to-day operations of a specific function or department within the organization, such as finance, marketing, or human resources. A functional management may provide input or feedback on the requirements elicitation process or technique, but does not have the authority to dictate it. A project sponsor is a stakeholder who is responsible for initiating, funding, and supporting the project or the solution. A project sponsor may approve or endorse the requirements elicitation process or technique, but does not have the authority to dictate it. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, page 175-176.

Engaging Stakeholders in Elicitation and Collaboration, paragraph 4

Top 10 Most Common Requirements Elicitation Techniques, paragraph 2

A Review of Fundamental Tasks in Requirements Elicitation, paragraph 1

Assessing capability gaps is a task of enterprise analysis that involves analyzing the current state of the organization and comparing it with the desired future state. The purpose of this task is to identify the new capabilities that the organization needs to acquire or enhance in order to meet the business need and achieve the organizational goals and objectives. These new capabilities can be related to processes, systems, people, or resources. Assessing capability gaps can help to determine the scope and feasibility of the solution, as well as the risks and benefits associated with it. References: BABOK Guide v3, page 25; CBAP / CCBA Certified Business Analysis Study Guide, page 69.

 Work performance information is the input of Monitor and Control Risks that acquires information from performance measurements and evaluates it to provide variance analysis and forecasting. Work performance information includes information such as the status of deliverables, implementation status for change requests, and forecasted estimates to complete. This information helps the business analyst to monitor and control the risks associated with the project and the solution. References: BABOK® Guide, p. 116; Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 3, Week 2, Video: “Risk Analysis and Management”

The type of analysis that would help the BA gain approval to proceed with creating this type of training program for this team is cost benefit analysis, as this is a technique that helps to compare the expected costs and benefits of a proposed solution or change. Cost benefit analysis can help the BA to demonstrate the value and feasibility of the training program, as well as the potential risks and impacts of not implementing it. By showing the positive return on investment and the alignment with the business objectives and needs, the BA can persuade the decision makers and stakeholders to approve the training program. References: The answer can be verified from the following sources:

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 7: Strategy Analysis, p. 232-233; Chapter 10: Cost Benefit Analysis, p. 352-355.

Business Analysis for Practitioners: A Practice Guide, Chapter 6: Solution Evaluation, p. 159-160.

 A process configuration is a type of flowchart that shows all the processes and the interfaces that interact with the project processes. A process configuration provides a visual overview of the project scope, boundaries, inputs, outputs, and dependencies. It helps the business analyst to understand the project context, identify the stakeholders, and define the requirements. A process configuration is different from a Pareto chart, which is a type of chart that shows the frequency and impact of problems or issues in a process. A Pareto chart helps the business analyst to prioritize the problems or issues and focus on the most significant ones. A process configuration is also different from a control chart, which is a type of chart that shows the variation and performance of a process over time. A control chart helps the business analyst to monitor and control the process quality and identify the causes of variation. A process configuration is not a quality baseline, which is a document that defines the quality standards and criteria for the project or the solution. A quality baseline helps the business analyst to measure and evaluate the quality of the requirements and the solution. A process configuration is not a RACI chart, which is a type of matrix that shows the roles and responsibilities of the stakeholders in a project or a process. A RACI chart helps the business analyst to clarify the expectations and accountabilities of the stakeholders and improve the communication and collaboration among them. References:

[CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition], Chapter 6: Enterprise Analysis, page 217-218.

Business Analysis: Key Definitions & Strategy Analysis, paragraph 3

Business Analysis: Process Modeling, paragraph 1

Process Configuration - an overview | ScienceDirect Topics, paragraph 1

Process Configuration - Project Management Knowledge, paragraph 1