While reviewing a subset of requirements with stakeholders, a business analyst (BA) finds a requirement that does not deliver benefit to any of the stakeholders.
After much discussion, the stakeholders decide that the requirement does not align with the solution scope.
What recommendation will the BA make?
When a requirement is identified as not delivering any benefit to stakeholders and does not align with the solution scope, the logical course of action is to eliminate the requirement. Updating the solution design, re-evaluating the future state, or changing the solution scope are not appropriate recommendations in this context because they do not address the fundamental issue of the requirement's lack of value and alignment with the solution. Eliminating the requirement simplifies the project and ensures that effort is focused only on requirements that provide actual stakeholder benefits and align with the intended solution.
I think D is the correct answer because the 1 - requirement does not deliver benefit to any the stakeholders and 2 - it does not align with the solution scope.
Answer C--Change the solution scope. Based on the line in question "After much discussion, the stakeholders decide that the requirement does not align with the solution scope."
D: A requirement can be of benefit to a stakeholder and still not be a desirable part of a solution. A requirement that does not deliver benefit to a stakeholder is a strong candidate for elimination. When requirements do not align, either the future state must be re-evaluated and the solution scope changed, or the requirement removed from the solution scope. If a design cannot be validated to support a requirement, there might be a missing or misunderstood requirement, or the design must change.
Ans: D - Eliminate the requirement. A requirement that does not deliver benefit to a stakeholder is a strong candidate for elimination. BABOK v3 7.3.4.3 pg. 146
This to me could be C or D. BABOK v3 7.3.4.3 Evaluate Alignment with Solution Scope: A requirement can be of benefit to a stakeholder and still not be a desirable partof a solution.
Con’t: A requirement that does not deliver benefit to a stakeholder is a strong candidate for elimination. When requirements do not align, either the future state must be re-evaluated and the solution scope changed, or the requirement removed from the solution scope. If a design cannot be validated to support a requirement, there might be a missing or misunderstood requirement, or the design must change. Please provide me your thoughts.
D=Eliminate the requriement beacuse only after eliminating it you are able to re-evaluate and update or change solution scope
D. You would change solution scope if as BABOK says' A requirement can be of benefit to a stakeholder and still not be a desirable part of a solution' . However, if it is of no benefit to any stakeholder, 'A requirement that does not deliver benefit to a stakeholder is a strong candidate for elimination" . You eliminate it
seems A
V3 7.3.4.3 PG 146