When organizations are new to the idea of using business analysts (internal or external), their first question often is: what would I get from a business analyst? What do they actually produce?
After all the words about eliciting information, understanding business problems, breaking down complexity, we, humans, want some concrete answers.
Business managers in charge of funding want to know what they will get for the money spent on employing someone to “do business analysis”.
Here are a few tangible things you should get.
Requirements captured in a variety of formats.
This could be business requirements documents, user story maps and backlogs, use case specifications.
Wireframes, mock-ups, prototypes.
These may be created to visualize forms, screen flows, report or dashboard design.
Documentation, training materials, presentations.
Different types of documentation may be needed to support the change – a solution overview for User Acceptance Testing, a business logic document, a user manual, presentations for training and implementation purposes.
Test scenarios, acceptance criteria.
Often, business analysts create, consult, or review QA documentation – from recommended test scenarios to detailed test case steps, expected results and acceptance criteria for UAT (User Acceptance Testing).
And one less tangible, yet the most important deliverable:
Building a shared understanding of business requirements by all stakeholders.
What do business analysts do to create these deliverables? They apply a number of business analysis tools and techniques – choosing the best one for each situation, sometimes experimenting a little. Choosing the right technique for each circumstance and audience is a sign of an experienced business analyst with a developed BA mindset.