How do you plan and run a requirements workshop?
What the interviewer wants to hear
- Clear objective and the right participants
- Agenda, pre-reading and ground rules
- Use structured techniques, such as process walkthroughs or silent brainstorming
- Manage dominant voices and keep to time
- Capture decisions, open questions and actions
- Share outputs quickly for confirmation
Model answer
I start with a clear objective, such as agreeing the to-be order process or the top requirements for a release. Then I choose participants who can represent each important view and make decisions, usually no more than 8 to 10 people. I send an agenda and any pre-reading, like the current process map. In the session I set ground rules, explain the goal and use structured techniques: walking through a process on a whiteboard or Miro, silent brainstorming on sticky notes, and dot voting to prioritise. I manage dominant voices with round-robin turns and park side topics. Throughout, I capture decisions, open questions and actions with owners. Before closing I read back what we agreed. I share the outputs within a day so people can correct anything while it is fresh, then follow up on the open items.
Can you answer it under time pressure?
Take a timed medium round and get scored on every answer.
More medium Business Analyst questions
- How do you work with a stakeholder who does not know what they want?
- How do you help stakeholders prioritise requirements?
- What is your role in user acceptance testing?
- Describe how you would use data to support a business recommendation.
- How does the business analyst role work in an agile team?
- Walk me through how you would model a business process using BPMN.
- How do you manage changes to requirements once development has started?
- How do you use SQL or data analysis in your work as a business analyst?
- How do you elicit and write non-functional requirements?