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?

The BA should recommend to eliminate the requirement that does not deliver benefit to any of the stakeholders and does not align with the solution scope. This is because the requirement is not necessary, valuable, or feasible, and it may introduce unnecessary complexity, cost, or risk to the solution. Eliminating the requirement would help to optimize the solution and ensure that it meets the stakeholder needs and expectations. Updating the solution design, re-evaluating the future state, or changing the solution scope are not the best options because they do not address the root cause of the problem and may result in scope creep or rework. Reference: CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Requirements Life Cycle Management, page 115 Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 3: Requirements Life Cycle Management, section 3.6: Assess Requirements Changes, page 64