IIBA CBAP Actual Questions

Prioritizing requirements is a process that helps business analysts and stakeholders to rank the requirements according to their importance, value, urgency, and dependency. Prioritizing requirements helps to ensure that the most critical requirements are addressed first, and that the available resources are allocated effectively. Prioritizing requirements also helps to manage the scope, schedule, and budget of the project, and to deal with changes and uncertainties. Prioritizing requirements is not only about determining the cost or the schedule of each requirement, but also about understanding the impact and the benefit of each requirement on the business need and the solution. Prioritizing requirements is not only about identifying the risks associated with each requirement, but also about mitigating or avoiding those risks by choosing the best solution option. References:

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section 10.31.3.11

Why Prioritise Requirements – How to do it and Why it is Critical to Project Success – BusinessAnalystMentor.com, paragraph 1

Why You Should Prioritize Requirements - ArgonDigital, paragraph 1

What Is Requirements Prioritization? Definition & Examples - airfocus, paragraph 1

Business analysts : How to prioritize requirements - Adaptive US, paragraph 1

A RACI chart is a tool that helps to define and clarify the roles and responsibilities of different stakeholders in a project or a process. It stands for Responsible, Accountable, Consulted, and Informed, which are the four types of tasks or activities that stakeholders can be involved in. A RACI chart is a matrix that lists the tasks or activities in the left column and the stakeholders or roles in the top row. For each task or activity, the RACI chart indicates who is Responsible, Accountable, Consulted, or Informed by using the letters R, A, C, or I. A RACI chart can help to improve communication, collaboration, and accountability among stakeholders, and to avoid confusion, duplication, or conflict of roles. A RACI chart can be used as part of the stakeholder analysis process, which is the process of identifying, categorizing, and assessing the stakeholders of a project or a process, and understanding their needs, expectations, and interests.

References:

RACI Chart - a how to guide to using RACI, paragraph 1

How the RACI Matrix Streamlines Stakeholder Engagement, paragraph 1

Stakeholder Wrangling 101: The RACI Framework, paragraph 1

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 30, section 2.51

An assumption is something that is believed to be true or certain to happen, without proof. Assumptions are often used to fill in the gaps of incomplete or uncertain information, and they can affect the analysis of the current and future states. In this question, the project manager is assuming that her project team members have a certain skill, without verifying it. This is an example of an assumption that should be identified and validated as part of the assessment of capability gaps.

The other options are not assumptions, but rather:

B. A constraint, which is a restriction or limitation that affects the performance or outcomes of a project or solution.

C. A requirement, which is a condition or capability needed by a stakeholder to solve a problem or achieve an objective.

D. A risk, which is an uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project or solution objectives.

References:

CBAP® Handbook, page 14, section 4.1.2.2

BABOK® Guide, page 30, section 3.2.1

CBAP / CCBA Certified Business Analysis Study Guide, page 94, section 3.2.1

A requirements trace matrix (RTM) is a tool that helps to ensure that the project’s scope, requirements, and deliverables remain consistent and aligned throughout the project lifecycle. It traces the requirements from their origin to their fulfillment by linking them to other project artifacts, such as design documents, test cases, and solution components. An RTM can also be used to verify that all requirements are met and to identify changes to the scope when they occur. An RTM is especially useful for smaller projects where there are few requirements, as it can help to track the progress and status of each requirement and avoid scope creep. A requirements trace matrix is not the same as a roles and responsibility matrix (A), a RACI matrix (B), or a coverage matrix ©, which are different types of matrices that serve different purposes in project management. References:

IIBA BABOK Guide v3, p. 30, 176, 264

Requirements Traceability Matrix – RTM - Project-Management.com

CBAP/CCBA/ECBA Certification Practice Test | MindsMapped, Question 6