5 Reasons QA Should be Involved in Requirement Gathering

Most of the focus in managing software requirements has centered on Users and Developers. It seems obvious to do so, doesn’t it? Users are the ones who will use the project, may also be the ones asking for the project, and thus are typically the ones we focus on in requirements elicitation processes. Developers take those requirements; transform the concepts, rules, models, and statements into code; and produce a solution that hopefully does what was defined at the start of the project.