collaborative - we work closely with software developers, stakeholders, and software testers and rely less on comprehensive requirements documentation at the inception of the project.

flexible and adaptable - unlike a more traditional software development project, through agile business analysis, we welcome changes in requirements. being agile means that changing requirements is not made difficult because of extensive documentation, communication cycles or change management processes.

just in time requirements - through agile business analysis, we know what is the right amount of requirements documentation to gather for a development cycle or iteration.

more face to face meetings - because agile business analysis focuses on less documentation and more face to face meetings or interviews with stakeholders, software developers or testers, we are able to make use of more user stories and less user cases for documenting requirements.

iterative development - unlike requirements management, practiced in a traditional waterfall software development life cycle, we only focus on gathering, analyzing or validating the requirements needed in each iteration.