IIBA Certificate of Capability in Business Analysis CCBA Exam Questions

Answer : C

MoSCoW is a prioritization technique used in business analysis and project management to categorize requirements into four levels of priority: Must have, Should have, Could have, and Won't have.This method helps teams focus on the most critical requirements that need to be satisfied for a project to be successful, while also identifying which requirements can be deferred or excluded if necessary.

Must have: These are non-negotiable requirements that are essential for the project's success. If these are not met, the project is considered a failure.

Should have: These are important but not critical requirements. They are high-priority items that can be scheduled for a future release without impacting the current one.

Could have: These are desirable requirements that do not affect the overall success of the project. They can be included if time and resources permit.

Won't have: These are the lowest priority requirements or those that are not necessary for the current delivery cycle. They are recognized but not planned for the current project timeline.

Answer : D

The allocation of requirements is not an input to the solution scope definition, but a task that will use the solution scope as an input. The allocation of requirements is the process of assigning the requirements to solution components, such as features, functions, modules, etc. The allocation of requirements helps to ensure that the solution components are aligned with the requirements and that the requirements are traceable throughout the project lifecycle. The other options are correct inputs to the solution scope definition, as they provide the information and guidance needed to define the boundaries and characteristics of the solution that will address the business problem or opportunity. The required capability describes what the solution must be able to do to meet the stakeholder needs. The assumptions and constraints identify the factors that affect the feasibility, desirability, or viability of the solution. The business need defines the problem or opportunity that the solution aims to resolve or exploit.Reference:

Solution Scope -- An Insight

BABOK Chapter 7: Requirements Analysis and Design Definition

The quick guide to defining project scope---in 8 steps

Answer : A

Functional decomposition is a technique that involves breaking down the solution scope into smaller units for allocation. It helps to organize and structure the requirements and the solution components into a hierarchical model that shows the relationships and dependencies among them. Functional decomposition helps to simplify complex problems, to identify gaps and redundancies, and to assign responsibilities and resources.

Answer : D

According to the BABOK Guide, high quality requirements should have the following characteristics: atomic, complete, consistent, concise, feasible, unambiguous, testable, prioritized, and traceable. Cohesive, consistent, and complete are among these characteristics, while constrained is not. Constrained means that the requirements are limited by some factors, such as budget, time, or resources, which may affect their quality negatively.Reference:BABOK Guide, section 4.2.5, page 98;CCBA Handbook, section 4.4, page 6.

Answer : C

Comprehensive and Detailed Requirements management toolsprovidea structured way to document requirement changes, maintain traceability, and track approvals.

BABOK Guide (Chapter 5.1 - Trace Requirements)states thattraceability ensures every requirement is linked to its origin and tracks changes throughout the project lifecycle.

Risk analysis and management (Option A)addresses uncertainties but does not document requirement history.

Acceptance and evaluation criteria (Option B)define success conditions but do not track approvals.

Legal and regulatory information (Option D)ensures compliance but does not track requirement history.

Answer : C

The assess capability gaps task is a part of the business analysis planning and monitoring knowledge area. It involves comparing the current state and future state of the organization to identify the differences or gaps that need to be addressed by a solution. These gaps represent the new capabilities that the organization requires to achieve its business goals and objectives. The assess capability gaps task helps the business analyst to define the scope of the solution, prioritize the requirements, and plan the business analysis approach.Reference:

Business Analysis Body of Knowledge (BABOK) Guide Version 3, page 36-37

Business Analysis Driving Business Success, page 5-6

Answer : D

A vision statement is a document that states the business need, identifies the key stakeholders, and defines the positive impact the solution will bring to the organization and stakeholders. A vision statement provides a high-level description of the desired future state and the value proposition of the solution.It also helps to align the expectations and objectives of the stakeholders and to guide the scope and direction of the project12.

The other options are not correct because:

Requirements documentation is a document that describes the capabilities, features, and qualities of the solution that will meet the stakeholder needs.It does not state the business need or the positive impact of the solution3.

Business case is a document that provides the justification for initiating a project or task. It typically includes the business need, the expected benefits, the costs, the risks, and the alternatives of the proposed solution.It does not identify the key stakeholders or define the positive impact of the solution4.

Project charter is a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It typically includes the project purpose, objectives, scope, deliverables, milestones, roles and responsibilities, budget, and risks.It does not state the business need or the positive impact of the solution5.

Vision Statement, section ''Description of Change''

How to Write a Vision Statement for Your Business, section ''What is a vision statement?''

Requirements Documentation, section ''Description of Change''

Business Case, section ''Description of Change''

Project Charter, section ''Description of Change''