Business Analysis Fundamentals
What a BA Does
Section titled “What a BA Does”- Bridges business stakeholders and technical teams
- Elicits, documents, and validates requirements
- Ensures the solution solves the right problem
Requirements Types
Section titled “Requirements Types”| Type | Description | Example |
|---|---|---|
| Functional | What the system does | ”User can filter invoices by date” |
| Non-functional | How the system performs | ”Page loads in < 2s” |
| Business | Why we’re doing it | ”Reduce manual data entry by 80%“ |
Core Techniques
Section titled “Core Techniques”- Stakeholder interviews — understand pain points, not just requests
- Process mapping — AS-IS vs TO-BE flows
- Use cases / user stories — As a [role], I want [action], so that [benefit]
- Gap analysis — what’s missing between current and desired state
BA Toolkit
Section titled “BA Toolkit”- BPMN for process diagrams
- User story mapping
- MoSCoW prioritization (Must / Should / Could / Won’t)