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

 The project manager must be consulted regarding the changes to the business analysis approach before they are implemented in this project. The project manager is responsible for planning, executing, monitoring, controlling, and closing the project activities within the constraints of scope, time, cost, quality, resources, and risk. The project manager also coordinates with other roles such as business analysts, developers, testers, sponsors, and end users. Therefore, any changes to the business analysis approach must be discussed with the project manager to ensure alignment with the project objectives and plan. References: : Project Manager Role : Project Manager Responsibilities

 Requirements architecture is a technique that organizes and structures requirements into a coherent whole, using a combination of text and models1. Requirements architecture can help the BA to model the requirements for the review by showing the relationships, dependencies, and priorities among the requirements2. Requirements architecture can also help the BA to communicate the requirements to the stakeholders in a clear and consistent way3. The other options are not guidelines or tools for modeling the requirements. Current state description is a technique that describes the existing situation or environment of an organization or a stakeholder4. Methodologies and framework are sets of methods, principles, and practices that guide the business analysis work. Domain knowledge is the understanding of a specific subject matter or industry. References:

1: BABOK® Guide v3, p. 388

2: Requirements Architecture: A Framework for Clear Communication

3: Requirements Architecture: The Key to Successful Requirements Management

4: BABOK® Guide v3, p. 390

: BABOK® Guide v3, p. 12

: What is Domain Knowledge and Why is it Important?

 Interviews are a technique for eliciting information from stakeholders by asking questions and listening to their responses. Interviews can be used to identify and confirm the correct stakeholders for a project, as well as to understand their needs, expectations, and preferences. Functionaldecomposition, lessons learned, and risk analysis are useful for other aspects of business analysis, but they do not directly help to identify the correct stakeholders. References: IIBA CCBA Certification Exam Sample Questions - Process Exam, [BABOK® Guide v3], Chapter 4: Elicitation and Collaboration, Section 4.1: Plan Business Analysis Elicitation, p. 105.

“The solution will report the average number of days an account payment is outstanding” is an example of a key performance indicator (KPI). A KPI is a measurable value that demonstrates how effectively an organization or a solution is achieving its key business objectives or goals. KPIs can help to monitor and evaluate the performance of a solution or an organization over time, identify areas of improvement, and support decision making. The average number of days an account payment is outstanding is a KPI that measures how well the AP solution supports the goal of timely payment processing. References: : Key Performance Indicator (KPI)

The BA can suggest process improvement as a solution that the organization can consider to increase efficiencies. Process improvement is a technique for identifying and implementing changes to business processes that will enhance their effectiveness and efficiency2. Process improvement can help to eliminate or reduce workarounds, which are temporary or alternative ways of performing a task or process that bypasses a problem or limitation3. By improving the processes, the organization can achieve better outcomes, reduce costs, increase customer satisfaction, and gain competitive advantage. References: 2: BABOK Guide v3, Section 10.23 3: Workaround

The BA should assess the impact of the forthcoming legislation immediately when it is logged in the action items register. This is because assessing the impact of a change is a technique that involves analyzing how a change affects the existing or proposed solution, business processes, stakeholders, or organization. Assessing the impact of the forthcoming legislation immediately can help the BA to identify and mitigate any potential risks or issues that might have an impact on the proposed architecture and plan accordingly. The other options are not as urgent or appropriate as assessing the impact immediately. References:

BABOK Guide, section 10.16: Impact Analysis

CCBA Practice Test, question 115

The BA can find out which stakeholder has the authority to approve, deny, or defer the change request from the governance approach. The governance approach defines how decisions are made regarding business analysis activities and deliverables. It specifies who are involved in making decisions, what are their roles and responsibilities, what are the criteria and processes for decision making, and how decisions are communicated and documented. The governance approach can help to identify which stakeholder has decision-making authority over change requests. References: : BABOK Guide v3, Section 2.4

 A requirements management tool is a software application that helps the project team to maintain the traceability of requirements for a software system. A requirements management tool can store, organize, link, track, and report on the requirements and their attributes, such as status, priority, source, owner, and dependencies1. By using a requirements management tool, the project team can manage the large number of requirements more efficiently and effectively, and ensure that they are aligned with the business needs and the solution scope. A requirements management tool can also facilitate communication and collaboration among the stakeholders, and support other activities, such as planning, analysis, design, testing, and change management.

References: The answer is based on the BABOK® Guide, which is a key resource for the CCBA® certification. Specifically, it relates to the Requirements Life Cycle Management knowledge area, where maintaining requirements for reuse and traceability is a key task for the business analyst23. It also relates to the Techniques section, where requirements management tools are described as one of the techniques that can be used by the business analyst24. Additionally, the answer is supported by the web search results from the tool invocation, which provide more information and examples of requirements management tools.

 Requirements management tools provide a means to document traceability and change of requirements and designs. Requirements management tools are software applications that support the documentation, analysis, tracking, prioritization, approval, and change management of requirements4. They can help to establish relationships and dependencies among requirements, solution components, designs, tests, and other artifacts. They can also help to record and monitor changes to requirements and designs, as well as their audit and approval history. References: 4: BABOK Guide v3, Section 9.6

According to the BABOK® Guide, one of the goals of business analysis is to enable successful change that delivers value for stakeholders. Value can be defined as the worth, importance, or usefulness of something to a stakeholder within a context1. One of the ways to deliver value is to improve the experience of the customer, which is the external stakeholder who consumes or benefits from the products or services provided by the enterprise2. Improving the purchasing process is an example of an improvement opportunity that aims to enhance the customer experience, as it can make it easier, faster, or more convenient for the customer to buy the productsor services they need or want3. References: 1: BABOK® Guide, version 3, section 1.2, page 52: BABOK® Guide, version 3, section 2.2.2, page 163: BABOK® Guide, version 3, section 6.1.4, page 184.

 Product scope is the features and functions that characterize a product, service, or result1. It defines what the product or service will do and how it will meet the customer needs and expectations2. Product scope is different from project scope, which is all the work needed to deliver a product, service, or result as defined in product scope1. Requirements envisioning is a technique to collaboratively identify and define the high-level features and scope of a solution3. Requirements foundation is a term used by IIBA to describe the core concepts of business analysis, such as requirements, stakeholders, and business analysis planning and monitoring4. References:

Certification of Capability in Business Analysis (CCBA®) Handbook, page 5, section “4. Review the Exam Blueprint”

Business Analysis Expert Certification, CCBA® | IIBA®, section “BABOK® Guide v3”

Requirements Envisioning: An Agile Best Practice

Business Analysis Core Concept Model™ (BACCM™)

 A structured walkthrough is a process of reporting, verifying, and validating requirements with the involved stakeholders. The purpose of a structured walkthrough is to ensure that the requirements are clear, complete, consistent, and aligned with the business needs and objectives. The first step of a structured walkthrough is to identify the objectives and goals of the session, such as what requirements will be reviewed, what feedback is expected, and what outcomes are desired. This helps to set the expectations and scope of the walkthrough and to focus the discussion on the relevant topics. References:

Capability in Business Analysis™ (CCBA®) Certification, International Institute of Business Analysis (IIBA), 2020, p. 27.

Structured Walkthrough Sessions: Why Bother?, Business Analyst Learnings, 2017.

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)]

According to the BABOK® Guide, the business analysis approach is the plan that describes how the business analysis activities will be executed. To plan the business analysis approach, the business analyst must understand the organizational process needs and the objectives that apply to the initiative1. The organizational process needs are the policies, standards, and procedures that guide thebusiness analysis work. The objectives that apply to the initiative are the goals and expected outcomes of the project or program.

The other options are not correct because they are not necessary to plan the business analysis approach. Stakeholders’ threats and perceived threats, consideration of risk and reward, and purpose of the proposed solution are all aspects that may be considered during the business analysis activities, but they are not required to plan the approach itself.

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”