An experienced MATRIX Business Analyst (BA) can be worth their weight in gold. A good BA can elicit and document requirements just by having a simple conversation. A good BA knows the right questions to ask for clarification. A good BA can document your system. A good BA understands what everyone needs and wants on a project and can get it documented.

Central Source of Information

A BA acts as a central source of information for clients, developers, and testers, and here’s why:

• A BA writes requirements or user stories for the client so they can spend more time thinking about what they need and want instead of writing it all out.
• A BA writes design documents to capture how the developers have decided to implement the requirements.
• A BA provides support to trainers by providing all the information they have gathered and documented.
• And, because they know best what is being developed and how, a BA can also supplement the testing team.

Clear Documentation

You’re a busy person—do you have time to document your requirements or user stories for a project? Developers are busy people—they are busy designing and coding, and don’t typically have time to interact a lot with clients. The BA is the missing link to keep everything clearly documented for the client, developers, and testers. Without good documentation, it's difficult to know what to build or what was built.