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 to three times a year but require a high effort to implement. What should the BA recommend in this case?
If the proposed solution contains features that are rarely used but require significant effort to implement, it would be prudent to assign it a lower priority for a future release. This approach ensures that the initial release can focus on more critical and widely-used functionalities, optimizing resource utilization and addressing high-impact needs first. By deferring features with limited usage to future releases, the business can manage its efforts more efficiently while still acknowledging the importance of those features.
A- assign it a lower priority and move it to future phases
Assigning it a lower priority means the feature can still be considered for implementation but not in the initial release.
if a requirement needs high effort to implement or rarely used, it does not mean it has to be moved to a future release. The info. provided is not sufficient for A, hence it is B
This question is not very forthcoming. I could see this as being either A or B. Can anybody cite a source for this answer and help me understand?
Since the solution is only used 3 times a year not by all but by Few - Low Priority High Effort to Implement - High Priority. The implementation team can have it scheduled as a future release