It’s much easier to see the usefulness of BAs in traditional waterfall development environments where requirements have to be clearly defined in Requirements Specification Documents before system development can begin. In Agile environments however, users and developers are expected to sit in the same room and agree on what will be developed, with little emphasis on documentation. Is the BA role in Agile software development being threatened?