IIBA Updated CCBA Exam Questions and Answers by effy

According to the BABOK® Guide, a change-driven approach of business analysis is one that “emphasizes rapid delivery of business value in short iterations” (p. 31). This approach allows for frequent feedback and validation of the requirements and the solution, as well as adaptation to changing business needs and priorities. The project manager’s authority to approve the requirements based on the short iterations of business analysis activities indicates that this approach is being used in this scenario. The other options are not correct because:

Progressive elaboration is a technique of gradually refining the level of detail and accuracy of the requirements as more information becomes available, not an approach of business analysis (p. 36).

Plan-driven approach is one that “emphasizes upfront definition of the requirements and the plan to deliver the solution” (p. 31). This approach requires more formal approval and change control processes than the change-driven approach.

Iterative approach is a generic term that can apply to both plan-driven and change-driven approaches, as long as they involve repeating cycles of analysis and delivery (p. 31). It is not a specific approach of business analysis by itself. References:

BABOK® Guide, p. 31, 36

Business Analysis: Definition, Process, Techniques and Tips, section “What are the different types of business analysis techniques?”

According to the BABOK® Guide, transitional requirements are “the capabilities that the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but that will no longer be needed once the change is complete” (p. 36). Transitional requirements are defined in the Specify and Model Requirements task, which is part of the Requirements Analysis and Design Definition knowledge area. The inputs to this task are stakeholder management strategy, stated requirements, and organizational readiness assessment. The other options are not correct because:

A. Stakeholder management strategy is an input to the Specify and Model Requirements task, as it provides information on the stakeholder roles, responsibilities, communication preferences, and expectations for the requirements definition process (p. 110).

C. Stated requirements are an input to the Specify and Model Requirements task, as they are the initial set of requirements that are elicited from the stakeholders and need to be analyzed, modeled, and refined (p. 110).

D. Organizational readiness assessment is an input to the Specify and Model Requirements task, as it provides information on the current state of the organization, the readiness and resistance to change, and the potential impacts of the solution (p. 110). References:

BABOK® Guide, p. 36, 110

Transitional Requirements - Modern Analyst, section “What are Transitional Requirements?”

 Verification activities are used to check the quality and completeness of the requirements and to ensure that they meet the standards and criteria defined by the organization and the stakeholders. Verification activities should be performed iteratively throughout the requirements analysis process, as new requirements are elicited, analyzed, documented, and validated. This helps to identify and resolve any errors, inconsistencies, ambiguities, or gaps in the requirements as early as possible, and to avoid rework and waste.

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 techniques123. You can also find some useful resources and sample questions from other sources

According to the CCBA® Handbook, one of the tasks of the business analyst is to “define the business need” (p. 11). This task involves identifying and describing the problem or opportunity that the organization faces, and the desired outcomes that the solution should achieve. The inputs to this task are business goals and objectives, which are “the desired outcomes of a change initiative or the state of the enterprise after the successful implementation of a solution” (p. 35). Business goals and objectives provide the context and direction for the business analysis work, as well as the criteria for evaluating the value and benefits of the solution. The other options are not correct because:

B. Stakeholder identification and stakeholder analysis are not inputs to the define the business need task, but rather outputs of the plan business analysis approach task (p. 10). They provide information on the stakeholders who are affected by or have an interest in the business need and the solution, as well as their roles, responsibilities, communication preferences, and expectations.

C. Requirements and business analysis approach are not inputs to the define the business need task, but rather outputs of the elicit and specify and model requirements tasks (p. 11-12). They provide information on the capabilities and conditions that the solution must have and meet to address the business need, as well as the methods and techniques that the business analyst will use to perform the business analysis work.

D. Elicitation approach and solution approach are not inputs to the define the business need task, but rather outputs of the plan business analysis approach and determine solution approach tasks (p. 10-11). They provide information on the tools and techniques that the business analyst will use to gather and validate the requirements, as well as the type and scope of the solution that will be implemented to address the business need. References:

CCBA® Handbook, p. 10-12, 35

BABOK® Guide, p. 35, 106