IIBA Updated CCBA Exam Questions and Answers by hidayah

According to the BABOK® Guide, allocation is “the process of assigning stakeholder and solution requirements to solution components in order to provide a common understanding of the scope and value of each component” (p. 36). Allocation is a type of forward traceability, as it traces the requirements from their origin to their implementation in the solution. The other options are not correct because:

Lineage tracking is a type of backward traceability, as it traces the requirements from their current state to their source (p. 36).

Backwards pass is a term used in project management, not in requirements traceability. It refers to the process of calculating the late start and late finish dates for project activities (p. 215).

Derivation is another type of backward traceability, as it traces the requirements from their current state to their parent requirements (p. 36). References:

BABOK® Guide, p. 36, 215

Requirements Traceability: Definition, Why it matters & Tools, section “Forward Traceability”

 A requirements signoff process is a process of obtaining formal approval from the stakeholders that the requirements are clear, complete, consistent, and aligned with the business needs and objectives. A requirements signoff process is important because it helps to ensure that the stakeholders are satisfied with the requirements and that they agree to move forward with the solution development based on the requirements. A requirements signoff process also helps to avoid scope creep, rework, and conflicts that may arise from unclear or changing requirements12.

The other options are not correct because:

Option B is incorrect. A requirements signoff process does not confirm that the project sponsor and the project manager are in agreement with the business analyst about the accuracy and completeness of the requirements. A requirements signoff process involves all the stakeholders who have an interest or influence in the project or its outcome, not just the project sponsor and the project manager. The business analyst’s role is to facilitate the communication and collaboration among the stakeholders, not to impose their own views on the requirements3.

Option C is incorrect. A requirements signoff process does not hold stakeholders accountable for the cost and schedule of the requirements. A requirements signoff process is focused on the quality and validity of the requirements, not on the budget and timeline of the project. The cost and schedule of the requirements are determined by the project manager, who is responsible for planning, executing, monitoring, and controlling the project activities and resources4.

Option D is incorrect. A requirements signoff process does not allow the project manager to begin the project. A requirements signoff process is usually done after the project has been initiated and the business analysis activities have been conducted. The project manager can begin the project after the project charter has been authorized, which defines the project purpose, objectives, scope, deliverables, milestones, roles and responsibilities, budget, and risks5.

References:

3 Quick Tips for Requirements Sign-off - Business Analyst Learnings, section “3 Quick Tips for Requirements Sign-off”

How to Get Meaningful Sign-Off on Requirements - Bridging the Gap, section “How to Get Meaningful Sign-Off on Requirements”

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

What is Project Management | PMI, first paragraph

Project Charter, section “Description of Change”

According to the BABOK® Guide, a requirements trace matrix is a table that links requirements to their origin and traces them throughout the project life cycle. A requirements trace matrix is useful for tracking the status, priority, and satisfaction of requirements, as well as identifying dependencies, gaps, and overlaps. A requirements trace matrix is suitable for smaller projects where there are few requirements, as it can provide a simple and effective way to trace the few requirements for the project1. References: 1: BABOK® Guide, version 3, section 10.32, page 344.

 Solution performance assessment is not a task included in enterprise analysis, but rather in solution evaluation. Enterprise analysis focuses on identifying and defining the business need, assessing the capability gaps, determining the solution approach, defining the solution scope, and defining the business case. These tasks help the organization to align its strategic goals and objectives with the proposed initiatives and solutions. References:

What is enterprise analysis and what results does it have? | IIBA®

An Overview of Enterprise Analysis - Modern Analyst

Introducing Business Analysis Tasks | The International Institute of …