Exam CBAP topic 1 question 332 discussion

Option A. Stability. BABOK 5.3.4.1 - Basis for Prioritization: "Stability: the likelihood that the requirement will change, either because it requires further analysis or because stakeholders have not reached a consensus about it. If a requirement is not stable, it may have a lower priority in order to minimize unanticipated rework and wasted effort."

We cannot leave the requirement without prioritizing, so Option D is wrong. DSME doesn't have approval authority, either it's Sponsor or PM. In this scenario, PM is there who takes care of the scope of the project. Hence OPTION A Too much explanation? :-p

Yes, leaving priority unfilled for requirements is appropriate in CBAP when requirements are not yet stable, meaning they are still evolving or unclear. Prioritizing them prematurely could lead to wasted effort or rework. Instead, it's best to leave their priority unfilled until the requirements are better understood and clarified.

D. Leave priority unfilled for these requirements Why?: When requirements are not stable, it means they are still evolving or unclear. Prioritizing them prematurely—either high or low—could lead to misalignment, wasted effort, or rework. Instead, the best course of action is to leave their priority unfilled until the requirements are better understood, clarified, and stabilized. This approach: Respects the input of the SME. Avoids committing resources to uncertain work. Keeps the door open for re-prioritization once the requirement is ready.

The situation described involves unstable requirements that require further analysis to ensure they are well-defined and feasible. According to BABOK, when requirements are not stable or fully understood, the BA should aim to gather additional information and facilitate further discussions before assigning a priority. Here's why this is the best option: Avoid premature prioritization: Assigning a high or low priority prematurely (options A or B) could lead to wasted effort, as unstable requirements might change or require significant rework. Collaboration and alignment: The BA should work with the SME, project manager, and other stakeholders to clarify and stabilize the requirement before deciding on its priority. Avoid exclusion: Removing the requirement from the project entirely (option C) could overlook its potential importance, especially if it's critical from the SME's perspective.

Stability

Agree with answer A. Leaving requirement without priority will give you too much choices. An abundance of options can be problematic.

ans - A 5.3.4.1 Stability: the likelihood that the requirement will change, either because it requires further analysis or because stakeholders have not reached a consensus about it. If a requirement is not stable, it may have a lower priority in order to minimize unanticipated rework and wasted effort.

The Answer is A. BABOK pg 99 -Stability