A business analyst (BA) finds that the proposed solution has features used by a small group of stakeholders for business scenarios which may occur up…

The BA should recommend to assign the feature a lower priority for future release. This means that

the feature will not be included in the initial release of the solution, but it may be considered for

later releases depending on the availability of resources, the feedback from the stakeholders, and the

alignment with the business objectives. This approach can help to balance the value and the effort of

the feature, as well as to avoid scope creep and unnecessary complexity in the initial release. The

other options are not the best recommendations, as they may either ignore the needs of the

stakeholders, disrupt the existing business process, or increase the risk and cost of the

project. Reference:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Requirements Analysis

and Design Definition, Section 6.3: Prioritize Requirements, p. 255-256

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 6:

Requirements Analysis and Design Definition, Section 6.3: Prioritize Requirements, p. 155-156