Pass the IIBA Certification of Capability in Business Analysis CCBA Questions and answers with ExamsMirror

 A solution performance assessment is an output of the assess capability gaps process, not an input. A solution performance assessment evaluates how well the current or proposed solutions meet the business needs and objectives. It identifies the strengths and weaknesses of the solutions and provides recommendations for improvement1

The inputs of the assess capability gaps process are:

Enterprise architecture: This is a description of the structure, components, and relationships of the organization and its environment. It provides a holistic view of the current and desired states of the organization and its capabilities2

Solution scope: This is a statement that defines the boundaries and deliverables of the solution. It specifies what the solution will and will not include, and what problems or opportunities it will address3

Business need: This is a statement that articulates the problem or opportunity that the organization faces. It defines the gap between the current and desired states of the organization and its capabilities.

References: Business Analysis Body of Knowledge (BABOK® Guide), Section 6.1: Assess Capability Gaps, 6.1.3: Outputs; Business Analysis Body of Knowledge (BABOK® Guide), Section 6.1: Assess Capability Gaps, 6.1.2.1: Enterprise Architecture; Business Analysis Body of Knowledge (BABOK® Guide), Section 6.1: Assess Capability Gaps, 6.1.2.2: Solution Scope; [Business Analysis Body of Knowledge (BABOK® Guide)], Section 6.1: Assess Capability Gaps, 6.1.2.3: Business Need.

 Interface analysis is not an event-based elicitation technique. Event-based elicitation techniques are methods that use scenarios, simulations, or other types of events to elicit knowledge from experts or users. Some examples of event-based elicitation techniques are focus group, interview, workshop, critical incident technique, cognitive walkthrough, and protocol analysis12. Interface analysis, on the other hand, is a technique that examines the interactions and dependencies between a system and its external entities, such as other systems, users, or hardware3. Interface analysis is not based on events, but on the characteristics and requirements of the interfaces.

 Organizing requirements is the task of finding logical relationships and dependencies among the requirements and grouping them into coherent and manageable units. The two objectives of this task are to establish a structure for the requirements that facilitates communication, understanding, and traceability, and to establish a prioritization approach that is based on relevant criteria andstakeholder preferences. References: BABOK® Guide v3, page 120; Business Analysis Expert Certification, CCBA® | IIBA®, page 1.

 Assessing organizational readiness is a task that involves analyzing the impact of the proposed solution on the organization and the stakeholders, and identifying the gaps and risks that may affect the successful adoption and implementation of the solution. Beth is completing this task in this scenario, as she is considering the learning curve and the change management issues that the end users may face due to the new operating system, new office software, and new customized applications.

References: The information is verified as per the BABOK® Guide and related IIBA resources, which outline the standards and practices for business analysis. The BABOK® Guide is a key resource for understanding business analysis tasks and techniques1234. You can also find some useful resources and sample questions from other sources

 An organizational process asset is a term that describes the organizational policies, procedures, forms, and methodologies that the business analyst is to follow. These are the established practices and guidelines that the organization has developed and maintained over time, and they provide a framework for conducting business analysis activities. Organizational process assets may include templates, standards, checklists, tools, best practices, lessons learned, and other resources that can help the business analyst perform their tasks more efficiently and effectively.

References: The information is verified as per the BABOK® Guide and related IIBA resources, which outline the standards and practices for business analysis. The BABOK® Guide is a key resource forunderstanding business analysis inputs and outputs123. You can also find some useful resources and sample questions from other sources

 Project Communication Management is the knowledge area that covers the processes required to ensure timely and appropriate generation, collection, distribution, storage, retrieval, and ultimate disposition of project information. It involves planning, managing, monitoring, and controlling the communication activities and deliverables throughout the project lifecycle. Project Communication Management helps to keep the project stakeholders informed, engaged, and satisfied with the project progress and outcomes12.

The other options are not correct because:

Option B is incorrect. Identifying, defining, combining, unifying, and coordinating the various processes and project management activities with the Project Management Process Groups is the definition of Project Integration Management, not Project Communication Management. Project Integration Management is the knowledge area that covers the processes required to ensure that the various elements of the project are properly coordinated and aligned3.

Option C is incorrect. Managing timely completion of the project is the objective of Project Time Management, not Project Communication Management. Project Time Management is the knowledge area that covers the processes required to ensure that the project is completed within the agreed time frame.

Option D is incorrect. Organizing, managing, and leading the project team is the responsibility of Project Human Resource Management, not Project Communication Management. Project Human Resource Management is the knowledge area that covers the processes required to ensure that the project has the most effective and efficient human resources.

References:

Project Communication Management - Five Steps | PMI, section “Project communication management applies the general management skill of communication within the boundaries of the project being managed and the responsibilities of the project manager.”

What is Project Communication Management? | Wrike, section “What Is Project Communication Management?”

Project Integration Management - A Quick Guide | Simplilearn, section “What is Project Integration Management?”

[Project Time Management - Definition, Process, Steps, and Tools], section “What is Project Time Management?”

[Project Human Resource Management - A Short Guide | Simplilearn], section “What is Project Human Resource Management?”

 Brainstorming is an elicitation technique that involves generating a large number of ideas or options for solutions in a creative and collaborative way. Brainstorming is suitable for eliciting requirements from a large group of stakeholders, as it allows them to share their perspectives, opinions, and suggestions without any judgment or criticism. Brainstorming also helps to produce a broad set of options for solutions, as it encourages the participants to think outside the box and to build on each other’s ideas. Brainstorming can be done in various formats, such as face-to-face, online, or hybrid, and can be facilitated by a business analyst or a neutral moderator. The other options are not elicitation techniques that can achieve the same goal as brainstorming. Business rules analysis is a technique for identifying, documenting, and validating the rules that govern the behavior and operation of a business or a system. Benchmarking is a technique for comparing the performance, processes, orpractices of an organization or a system with those of other organizations or systems that are considered to be the best in the industry or the domain. Data flow diagrams are a technique for modeling the movement and transformation of data within a system or a process. References:

9 Elicitation Techniques Used by Business Analysts – Tips and Guidance

CBAP/CCBA preparation questions - The Functional BA

Business Analysis: The Elicitation Process - UniversalClass

Elicitation techniques in business analysis - PMWorld 360 Magazine

 The type of requirements organization that Ben is doing in this scenario is functional decomposition. This is a technique for breaking down a complex system or process into its constituent parts and describing their functions and interactions12. By taking the laser printer apart and identifying each component’s purpose, Ben is applying functional decomposition to understand the structure and behavior of the system. The other options are not types of requirements organization, but rather techniques for modeling different aspects of the system or process, such as the flow of activities (B), the boundaries and deliverables ©, or the data elements and relationships (D)3. References: Certification of Capability in Business Analysis™ (CCBA®), CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Business Analysis Expert Certification, CCBA® | IIBA®

 A work product is any artifact created or modified as part of the business analysis work, such as models, diagrams, matrices, documents, or presentations12. A work product can be used to communicate, analyze, verify, or validate the requirements, or to support decision making or problem solving3. Requirements documentation is not a work product, but a deliverable, which is a work product that is formally reviewed, agreed upon, and delivered to a stakeholder or customer4.Interview questions and notes, presentation slides, and meeting agendas and minutes are examples of work products that can be used to develop the requirements. References:

1: BABOK® Guide, Version 3.0, p. 10

2: Business Analysis Expert Certification, CCBA® | IIBA®

3: CCBA® and CBAP® Certifications Study Guide, Chapter 2

4: BABOK® Guide, Version 3.0, p. 11

 Lean and Six Sigma are both documented approaches to the business analysis work, as they provide methods and tools for improving business processes and delivering value to customers. Lean focuses on eliminating waste and optimizing the flow of value, while Six Sigma focuses on reducing variation and defects and enhancing quality. Both approaches are aligned with the BABOK® Guide principles and practices12. Deming’s Quality Circle and the Waterfall approach are not documented approaches to the business analysis work, but rather quality management and software development methodologies, respectively34. References: Business Analysis Expert Certification, CCBA® | IIBA®, CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, The Business Analysis Standard | KnowledgeHub IIBA®, CCBA: Certification of Capability in Business Analysis Study Guide

According to the Business Analysis Body of Knowledge® (BABOK® Guide), structural rules and operative rules are two types of business rules that govern the behavior and structure of an organization. Structural rules are rules that define the policies, standards, and guidelines that the organization follows as a matter of choice. They are often derived from the vision, mission, values, and goals of the organization. Operative rules are rules that define the logic and criteria that are used to determinethe truth or falsity of a statement or the membership of an entity in a category. They are often derived from the requirements, specifications, and constraints of the solution.

References: The information is aligned with the competencies and knowledge areas defined in the Business Analysis Body of Knowledge® (BABOK® Guide) and the Certification of Capability in Business Analysis™ (CCBA®) as provided by the International Institute of Business Analysis (IIBA®). For detailed references, please consult the CCBA® guide1 and the BABOK® Guide2 available through the IIBA® website and bookstore3. You can also find some useful resources and sample questions from other sources4.

 An onion diagram is a type of stakeholder map that shows the relative influence, impact, and relation of stakeholders by plotting them closer to or farther away from the solution. An onion diagram consists of concentric circles that represent different layers of stakeholder involvement and interest in the solution. The innermost circle contains the core team members who are directly responsible for the solution. The next circle contains the key stakeholders who have high influence and impacton the solution. The outer circles contain the secondary and tertiary stakeholders who have lower influence and impact on the solution, but still need to be considered and communicated with12.

The other options are not correct because:

A RACI matrix is a type of stakeholder map that shows the roles and responsibilities of stakeholders by assigning them to one of four categories: Responsible, Accountable, Consulted, or Informed. A RACI matrix does not show the relative influence, impact, and relation of stakeholders by plotting them closer to or farther away from the solution3.

A control chart is a type of statistical tool that shows the variation in a process over time and helps to identify the causes of variation. A control chart is not a type of stakeholder map and does not show the relative influence, impact, and relation of stakeholders by plotting them closer to or farther away from the solution4.

A tornado diagram is a type of sensitivity analysis tool that shows the effect of changing the value of one input variable on the output variable. A tornado diagram is not a type of stakeholder map and does not show the relative influence, impact, and relation of stakeholders by plotting them closer to or farther away from the solution5.

References:

Onion Diagram, section “Description of Change”

Stakeholder Mapping 101: A Quick Guide to Stakeholder Maps - ProjectManager, section “Onion Diagram”

RACI Matrix, section “Description of Change”

Control Chart, section “Description of Change”

Tornado Diagram, section “Description of Change”

The user stories approach for requirements organization is a technique that captures the stakeholder’s needs and expectations in a concise and structured format. A user story consists of three elements: a role, an action, and a benefit. It follows the template: "As a , I want to <action>, sothat "12. For example, “As a customer, I want to pay with a credit card, so that I can earn rewards points”. User stories help to identify the requirements that the solution will need to support, as well as the value proposition and the acceptance criteria for each requirement3. The other options are not accurate descriptions of the user stories approach for requirements organization. References:

1: BABOK® Guide, Version 3.0, p. 140

2: Tips for writing user stories as a business analysis professional | IIBA®

3: A Comprehensive Guide to CCBA Certification - Business Analysis Blog

A constraint is a restriction or limitation that affects the performance or value of a solution. Constraints can be related to time, cost, quality, scope, resources, or other factors. In this scenario, the customer’s demand that the solution should not cost more than $300,000 to implement and support for one year is a constraint that limits the possible options and trade-offs for the solution.

References: The information is aligned with the competencies and knowledge areas defined in the Business Analysis Body of Knowledge® (BABOK® Guide) and the Certification of Capability in Business Analysis™ (CCBA®) as provided by the International Institute of Business Analysis (IIBA®). For detailed references, please consult the CCBA® guide1 and the BABOK® Guide2 available through the IIBA® website and bookstore3. You can also find some useful resources and sample questions from other sources4.

A. The business analysis approach will be shaped by the problem or opportunity faced by the organization: This is a correct input for the business analysis approach, as it defines why the project is initiated and what are the desired outcomes and benefits for the organization and the stakeholders.

B. The business analysis approach will be shaped by the penalty of not seizing the opportunity: This is an incorrect input for the business analysis approach, as it is a consequence of not implementing the solution, not a factor that influences the planning and execution of the business analysis activities.

C. The business analysis approach will be shaped by the time allowed for business analysis planning: This is an incorrect input for the business analysis approach, as it is a constraint on the business analysis process, not an input. Constraints are restrictions or limitations that affect the feasibility, desirability, or viability of the solution.

D. The business analysis approach will be shaped by the risks faced by the organization: This is a correct input for the business analysis approach, as it identifies how the uncertainties and potential threats may affect the project’s objectives, scope, schedule, cost, or quality.