Business Analyst
Business analysts bridge the gap between business needs and technical solutions. This path covers the English for requirements workshops, writing clear user stories and use cases, facilitating stakeholder interviews, and producing documentation that both engineers and executives can act on.
Topics covered
- Requirements elicitation
- User stories & use cases
- BDD & acceptance criteria
- Stakeholder interviews
- Gap analysis
- Process documentation
Vocabulary spotlight
4 terms every Business Analyst should know in English:
The process of drawing out requirements from stakeholders through interviews, workshops, and observation
"During requirements elicitation, we discovered two user groups with conflicting needs."
The current state (as-is) and desired future state (to-be) of a process or system
"The as-is process takes 3 days manually; the to-be system automates it in seconds."
A prioritisation framework: Must have, Should have, Could have, Won't have
"We ran a MoSCoW workshop and cut 40% of the backlog from must-have to won't-have."
A specific, testable condition that a feature must meet to be accepted by the stakeholder
"The acceptance criterion is: the user receives a confirmation email within 30 seconds."
📚 Vocabulary Reference
Key terms organised by category for Business Analysts:
Requirements
Elicitation Techniques
Analysis
Documentation
Recommended exercises
Real-world scenarios you'll practise
- Running a stakeholder workshop to gather conflicting requirements
- Writing an acceptance criterion that both developers and testers can act on
- Presenting a gap analysis to senior management
- Challenging scope creep diplomatically with a business owner
🎯 Interview questions specific to this role
Practise answering these questions out loud — or in writing. Each question targets a real interviewer concern for Business Analysts.
- How do you handle conflicting requirements from different stakeholders?
- What is the difference between a use case and a user story?
- Walk me through how you would conduct a requirements workshop.
- How do you ensure your requirements are testable?
- How do you manage scope creep during a project?