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

The implementation subject matter expert is not a stakeholder who participates in the prioritization of requirements, because they are not directly affected by the business need or the solution. The project team, the domain subject matter expert, and the project manager are all stakeholders who have a vested interest in the outcome of the project and the value of the solution, and therefore they should be involved in the prioritization of requirements. References:

Business Analysis Expert Certification, CCBA® | IIBA®, section “Who can Become a CCBA?”

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), section 4.2.5 “Prioritize Requirements”

Decomposition is not an elicitation technique, but a technique for analyzing and structuring complex or large problems, processes, or systems into smaller and simpler components. Elicitation techniques are used to discover, explore, and communicate the needs and expectations of stakeholders. Examples of elicitation techniques are brainstorming, observation, prototyping, interviews, surveys, workshops, etc. References:

Certification of Capability in Business Analysis (CCBA) Handbook, page 10

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], pages 38-39, 50-51

The matrix documentation approach is used to specify and model requirements that are complex but uniform in structure. This means that the requirements can be broken down into simple elements that can be inputted into a matrix. A matrix is a rectangular array of numbers, symbols, or expressions, arranged in rows and columns. Matrices can be used to represent various types of requirements, such as data dictionaries, gap analysis, requirements traceability, and business rules analysis. Matrices can help to communicate information to a specific audience, confirm information, identify information gaps, and prevent the duplication of information. References:

Specifying and modeling requirements – The Functional BA

Selecting Requirements Documentation Techniques for Software Projects: a Survey Study

According to the CCBA® Handbook, one of the tasks of the business analyst is to “validate requirements to ensure that they are aligned with the business objectives and deliver value to stakeholders” (p. 11). Therefore, any requirements that do not deliver value to stakeholders should be removed from the requirements set, as they are unnecessary, irrelevant, or wasteful. The other options are not appropriate actions for the business analyst to take, as they do not address the issue of value alignment. References:

CCBA® Handbook, p. 11

BABOK® Guide, p. 35

When you assess a solution, what you are actually looking for is to determine the value of the proposed solution to the stakeholder requirements. This is the main purpose of the solution assessment and validation knowledge area, which involves measuring and evaluating the performance and benefits of the solution, and ensuring that it meets the stakeholder needs and expectations12. Value is defined as the worth, importance, or usefulness of something to a stakeholder within a context3. To determine the value of the proposed solution, you need to identify and analyze the value proposition, the value drivers, the value measures, and the value delivery4. The other options are not what you are actually looking for when you assess a solution, but rather aspects that may contribute to the value of the solution, such as the quality (B), which is the degree to which a solution meets the requirements and delivers the expected benefits5, the cost ©, which is the amount of resources expended or consumed to implement and operate the solution, or the accuracy (D), which is the extent to which a solution represents the true or exact state of the problem or the need. References: Business Analysis Expert Certification, CCBA® | IIBA®, Certification of Capability in Business Analysis™ (CCBA®), Business Analysis Certification Competencies, CCBA® | IIBA®, The Ultimate Guide to Business Capability Analysis, CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, [Certification of Capability in Business Analysis (CCBA®) - Simplilearn], [A GUIDE TO THE BUSINESS ANALYSIS BODY OF KNOWLEDGE]

 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”

Before managing the requirements, Tracy must identify the roles, responsibilities, and owners of the requirements, as this is one of the tasks under the business analysis planning and monitoring knowledge area1. This task involves defining who will be involved in the requirements developmentand management process, what their roles and responsibilities are, and who has the authority to approve or change the requirements. This helps to ensure clarity, accountability, and collaboration among the stakeholders and the business analyst. The other options are not prerequisites for managing the requirements, but rather activities that may be performed during or after the requirements analysis and design definition knowledge area2. Decomposing the requirements in WBS (A) is a technique for breaking down the requirements into smaller and more manageable components. Creating cost-benefits analysis of each requirement (B) is a technique for evaluating the value and feasibility of the requirements. Communicating the requirements to the stakeholders for their consent and approval (D) is a task for verifying and validating the requirements. References: CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS, Business Analysis Expert Certification, CCBA® | IIBA®

The task of verifying requirements is used to ensure that the requirements are ready for formal review and validation by the customers and for defining the information to allow additional work to be performed. This means that the requirements are checked for quality attributes such as clarity, completeness, consistency, testability, and traceability. The verification process also helps to identify any gaps, issues, or dependencies that need to be resolved or addressed before proceeding to the next phase of the business analysis work.

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 sources45.

Data modeling is a technique that involves creating a visual representation of the data and information relevant to the solution or business domain. It shows the concepts, attributes, and relationships that define the data and how they are organized and manipulated. Data modeling helps to organize requirements by providing a common understanding of the data and its structure, quality, and usage.

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 sources

According to the CCBA® Handbook, an implementation subject matter expert is “a stakeholder who has specialized knowledge of the technologies, tools, or techniques that will be used to implement the solution” (p. 15). They are involved in determining if the requirements can be implemented, as they have the technical expertise and experience to assess the feasibility, risks, and costs of the solution. They can also provide guidance and recommendations on how to best implement the requirements and achieve the desired outcomes. The other options are not correct because:

A. A domain subject matter expert is “a stakeholder who has in-depth knowledge of a specific aspect of the business domain” (p. 15). They are involved in defining and validating the requirements, as they have the business knowledge and insight to identify the needs, problems, and opportunities of the domain. However, they may not have the technical knowledge or authority to determine if the requirements can be implemented.

C. Project team members are “stakeholders who are responsible for the delivery of the solution” (p. 15). They are involved in implementing the requirements, as they have the skills and resources to execute the project plan and produce the solution deliverables. However, they may not have the technical knowledge or authority to determine if the requirements can be implemented.

D. A sponsor is “a stakeholder who authorizes the initiation of a project or initiative and provides the financial resources for it” (p. 14). They are involved in approving the requirements, as they have the decision-making power and influence to support the project or initiative. However, they may not have the technical knowledge or authority to determine if the requirements can be implemented. References:

CCBA® Handbook, p. 14-15

Identify Stakeholders for Requirements Gathering - Olive Technologies, section “Implementation Subject Matter Expert”

The project scope is the description of the work that needs to be done to deliver the project outputs and outcomes. It defines the boundaries, assumptions, constraints, deliverables, and acceptance criteria of the project12. The project manager is the stakeholder who is responsible for writing the project scope, as well as for planning, executing, monitoring, and controlling the project activities3. The business analyst, the domain subject matter expert, and the sponsor are other stakeholders who may contribute to the project scope definition, but they are not the ones who write it. References:

1: Project Scope Management | Project Management Professional (PMP)

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

3: [Project Manager Roles and Responsibilities | Project Management Professional (PMP)]

To answer this question, you need to compare the total cost of ownership (TCO) of the two solutions over time. The TCO is the sum of the initial cost and the recurring cost multiplied by the number of months. You can set up an equation to find the break-even point where the TCO of the two solutions are equal:

286,000 + 2,400x = 239,000 + 2,850x

Solving for x, you get x = 64. This means that after 64 months, the TCO of the two solutions will be the same. Therefore, you need to use your in-house solution for more than 64 months to be more cost effective than the vendor’s solution.

References:

Business Analysis Expert Certification, CCBA® | IIBA®, section “Business Analysis Planning and Monitoring”, subsection “Plan Business Analysis Approach”.

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), version 3, chapter 3, section 3.1.4.

A constraint is a restriction or limitation on the solution that is imposed by an external factor, such as a regulation, standard, or policy. Constraints must be identified and analyzed during the business analysis process, as they may affect the feasibility, desirability, or viability of the solution. Compliance officers are responsible for ensuring that the solution meets the relevant constraints and does not violate any laws or rules. References:

Certification of Capability in Business Analysis (CCBA) Handbook, page 6

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], page 30

The stakeholder register is the key output of the Identify Stakeholders process. It not only contains the names of the project stakeholders but also their goals, expectations, concerns, and other such details. The stakeholder register helps to plan, manage, and communicate with the stakeholders effectively and efficiently. The other options are not outputs of the Identify Stakeholders process, but inputs or outputs of other processes. The scope baseline, the project charter, and the project scope statement are all inputs or outputs of the Project Scope Management knowledge area, not the Project Stakeholder Management knowledge area. References:

Identify Stakeholders Process and Stakeholder Register

Chapter 13 - Stakeholder Management Flashcards

How to Identify Stakeholders in Project Management?

Brainstorming is a technique that involves generating as many ideas as possible in a group setting, without judging or evaluating them. The purpose of brainstorming is to stimulate creativity and innovation, and to explore different possibilities and perspectives. Setting a goal for the number of ideas to be generated in a brainstorming session is not advisable, as it may actually limit the ideas that can be generated. A goal may create a sense of competition or pressure among the participants, which may inhibit their creativity and willingness to share. A goal may also cause the participants to stop generating ideas once the goal is reached, even if there are more ideas to be discovered. Therefore, it is important for Brian to not set a goal for the number of ideas the group should generate in the session, but rather to encourage them to generate as many ideas as they can.

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 techniques and their applications across different contexts123. You can also find some useful resources and sample questions from other sources45.