What are the main documents or artefacts a business analyst produces?
What the interviewer wants to hear
- Stakeholder analysis
- Process models, such as as-is and to-be maps
- Requirements, such as a BRD, user stories or use cases
- Data models and data dictionary
- Traceability matrix
- Choose and tailor artefacts to the project
Model answer
It depends on the project, but common artefacts include a stakeholder analysis that shows who is involved and how to engage them, and process models, usually as-is and to-be maps in BPMN or swimlane form. For requirements, I might write a business requirements document on a traditional project, or user stories with acceptance criteria on an agile one, sometimes supported by use cases. I often create data models, a data dictionary and business rules, especially when reports or integrations are involved. A traceability matrix links requirements to their source and to tests. I may also produce a business case or options analysis and support UAT with scenarios. I always tailor the set to the project, because the aim is shared understanding, not paperwork.
Can you answer it under time pressure?
Take a timed easy round and get scored on every answer.
More easy Business Analyst questions
- What does a business analyst do?
- What techniques do you use to gather requirements?
- Explain functional and non-functional requirements with examples.
- How do you write a good user story and its acceptance criteria?
- What is process mapping and why is it useful?
- What is the difference between a business analyst and a product owner?
- How do you prepare for a stakeholder interview?
- What makes a requirement good?
- What is the difference between a use case and a user story, and when would you use each?