IIBA CCBA Exam Questions

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.Reference:

BABOK Guide, p. 31, 36

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

The BA should improve the stakeholder's ability to understand the requirements by following the IEEE/ISO 29148 requirements standards. This is because IEEE/ISO 29148 is an international standard that provides guidelines for developing good quality requirements. The standard covers aspects such as requirements processes, elicitation, analysis, documentation, validation, and management. Following the standard can help to ensure that the requirements are clear, complete, consistent, traceable,verifiable, and modifiable. The other options are not as effective or comprehensive as following the standard.Reference:

IEEE/ISO 29148: Systems and software engineering --- Life cycle processes --- Requirements engineering

CCBA Practice Test, question 101

Positive risk ranking is a basis for prioritization that allows the project team to work initially with lower-risk requirements first. Positive risk ranking is a technique that assigns a score to each requirement based on the level of risk associated with it, where a higher score indicates a lower risk and a lower score indicates a higher risk. The requirements are then prioritized in descending order of their scores, so that the project team can focus on the requirements that have the least uncertainty, complexity, or volatility first, and defer the requirements that have the most uncertainty, complexity, or volatility later.Positive risk ranking helps to reduce the likelihood and impact of potential problems, issues, or changes that may affect the requirements or the solution12

Option A is incorrect because quantitative ranking is not a basis for prioritization that allows the project team to work initially with lower-risk requirements first, but a technique that uses numerical values to compare and rank the requirements based on multiple criteria, such as value, cost, risk, urgency, dependency, etc.Quantitative ranking does not necessarily prioritize the lower-risk requirements first, but the requirements that have the highest overall score based on the weighted criteria34

Option C is incorrect because relationship to other requirements is not a basis for prioritization that allows the project team to work initially with lower-risk requirements first, but a factor that considers the dependencies and interdependencies among the requirements, such as prerequisite, co-requisite, or conflicting requirements. Relationship to other requirements does not necessarily prioritize the lower-risk requirements first, but the requirements that have the most influence or impact on the other requirements.

Option D is incorrect because implementation difficulty is not a basis for prioritization that allows the project team to work initially with lower-risk requirements first, but a factor that considers the effort, time, resources, and skills required to implement the requirements. Implementation difficulty does not necessarily prioritize the lower-risk requirements first, but the requirements that have the least difficulty or complexity to implement.

Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed, Section 8.5: Prioritization, p. 101-102.

Certification of Capability in Business Analysis (CCBA) - Simplilearn, Module 7: Requirements Analysis and Design Definition, Lesson 7.5: Define Transition Requirements, p. 6-7.

Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed, Section 8.5: Prioritization, p. 102-103.

Certification of Capability in Business Analysis (CCBA) - Simplilearn, Module 7: Requirements Analysis and Design Definition, Lesson 7.5: Define Transition Requirements, p. 8-9.

[Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed], Section 8.5: Prioritization, p. 100-101.

[Certification of Capability in Business Analysis (CCBA) - Simplilearn], Module 7: Requirements Analysis and Design Definition, Lesson 7.5: Define Transition Requirements, p. 10-11.

[Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed], Section 8.5: Prioritization, p. 100.

[Certification of Capability in Business Analysis (CCBA) - Simplilearn], Module 7: Requirements Analysis and Design Definition, Lesson 7.5: Define Transition Requirements, p. 12-13.

When you assess a solution, what you are actually looking for isto 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.Reference: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]

According to the BABOK Guide, the task of prioritizing requirements assesses the value, urgency, dependencies, and risks associated with requirements and designs to ensure that analysis and delivery work is done on the most important ones at any given time1. Prioritization is an ongoing process, with priorities changing as the context changes. The task of prioritizing requirements creates just one output, which isrequirements (prioritized).This output is a list or a model of requirements and designs that have been assigned a level of importance or urgency relative to other requirements and designs2.The output of requirements (prioritized) is used as an input for other tasks, such as managing solution scope and requirements, assessing proposed solutions, allocating requirements, and validating requirements3.

The other options are not correct outputs of the task of prioritizing requirements:

Validated requirements are an output of the task of validating requirements, which ensures that the requirements and designs support the delivery of value, fulfill the stakeholder needs, and meet the quality standards3.

Requirements rankings are not a formal output of the task of prioritizing requirements, but rather a possible technique to assign a numerical value to each requirement or design based on a set of criteria2.

Requirements assessment is not an output of the task of prioritizing requirements, but rather a possible technique to evaluate the impact, feasibility, and value of requirements and designs2.Reference:

2: CCBA and CBAP Certifications Study Guide, section Task: Prioritize Requirements, page 1

3: BABOK Guide, section 4.5 Prioritize Requirements, page 72

1: Prioritize Requirements and Designs1, page 1