During a prioritization meeting, a business analyst (BA) mentioned that the access management system requirements are not stable. The project manager and a team lead proposed removing the requirements from discussion. A domain subject matter expert (SME) insisted on making that requirement a high priority, because it is really important from their point of view.
What should the BA do?
The business analyst should make the requirement a lower priority to minimize unanticipated rework and wasted effort. When requirements are not stable, they are likely to undergo changes as further analysis is conducted or consensus is reached among stakeholders. Prioritizing such unstable requirements can lead to inefficiencies. It is more practical to address more stable requirements first and revisit unstable ones later once they are more defined and agreed upon.
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
The Answer is A. BABOK pg 99 -Stability
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.
Agree with answer A. Leaving requirement without priority will give you too much choices. An abundance of options can be problematic.
Stability