CAPM Practice: Determine how to gather requirements

Even technically infeasible requirements represent real business needs worth understanding. BAs should document them, explore workarounds, and keep them visible — technology or budget constraints may change, making previously infeasible requirements possible.

**Why not A:** Accepting technically impossible requirements without question sets the project up for failure. A business analyst has a professional obligation to assess feasibility and raise concerns rather than blindly agreeing to demands that cannot be delivered. Accepting such requirements wastes resources and erodes stakeholder trust when they inevitably cannot be fulfilled.

**Why not B:** Simply documenting impossible requirements as out of scope and never revisiting them is too rigid and dismissive. Requirements that appear technically impossible today may become feasible through alternative approaches, phased delivery, or evolving technology. The BA should work collaboratively with stakeholders to explore workarounds rather than permanently closing the door.

**Why not C:** Telling stakeholders their requirements are unreasonable is unprofessional and counterproductive. Even when a requirement cannot be implemented as stated, the BA should communicate constraints diplomatically while exploring the underlying business need. A confrontational approach damages the working relationship and may cause stakeholders to disengage from future requirements activities.