Stop Gathering RequirementsJuly 10, 2012
The concept of “gathering requirements” comes from the premise that there are requirements out there someplace that the business analyst has to find. But do users or stakeholders really have requirements? In this article, Steve Blais says that users don’t have requirements, so business analysts have to stop gathering requirements. His opinion is that user have business problem to solve. Requirements are defined or created by the business analyst as a possible solution to a business problem. The requirements document is the representation of the complete and accurate statement of what must be done to solve the business problem.