Business Analysis Fundamentals
Requirements, process mapping, user stories and stakeholder management.
Taught by Kritika Lama · Product Manager
What you'll learn
- Identify and classify stakeholders with a power/interest grid and a RACI matrix, and plan how to engage each group
- Plan and run elicitation interviews and workshops that uncover underlying needs, not just requested features
- Map as-is and to-be processes with swimlane diagrams and document the gaps between them
- Write business, functional and non-functional requirements that are clear, unambiguous and testable
- Turn requirements into INVEST user stories with Given/When/Then acceptance criteria
- Prioritise requirements with MoSCoW and trace each one from business need to test case
About this course
Business analysis is one of the steadiest roles in any organisation: every new system, process change or product feature needs someone who can find out what people actually need and write it down so it can be built and tested. This course is for aspiring and junior business analysts, product owners, developers and project staff who want a practical, structured method. You will learn to identify and manage stakeholders, run elicitation interviews and workshops, map as-is and to-be processes with swimlane diagrams, write clear BRDs and FRDs, turn needs into user stories with testable Given/When/Then acceptance criteria, sketch UML-lite diagrams, prioritise with MoSCoW and keep a requirements traceability matrix. The content draws on key knowledge areas of the IIBA BABOK Guide, so it is a useful foundation for the ECBA or CCBA. Independent study material — not affiliated with or endorsed by IIBA. Some workplace experience helps, but no prior BA training is needed.
Course content
7 lessons- 1What a Business Analyst Actually DoesThe BA role, the core concepts behind every change, and how the work fits agile and traditional projects.Preview
- 2Stakeholder Analysis and EngagementFind everyone affected by a change, map their power and interest, and plan how to involve each group.
- 3Elicitation: Getting to the Real NeedInterviews, workshops, observation and document analysis, plus questions that separate needs from solutions.
- 4Process Mapping: As-Is, To-Be and the GapScope a process with SIPOC, draw swimlane maps and document the gap between today and the future state.
- 5Writing Requirements: BRD, FRD and Non-FunctionalLevels of requirements, what goes in a BRD versus an FRD, and how to write statements that can be tested.
- 6User Stories and Acceptance CriteriaWrite INVEST user stories, split them to sprint size and define done with Given/When/Then criteria.
- 7UML-Lite, Prioritisation and TraceabilitySketch sequence and use case diagrams, prioritise with MoSCoW and keep requirements traceable through change.