Business Analysis 101: BA Foundations Role of BA in Agile Waterfall and Hybrid Projects

What This Is

The role of the Business Analyst (BA) in Agile, Waterfall, and Hybrid projects is the same core purpose – to discover, shape, and communicate the right solution for the business – but the way the work is organized, paced, and documented changes with the delivery method.
Real‑world example: A global insurer wants to replace its legacy claims‑processing system with a new cloud‑based CRM. In a Waterfall rollout the BA would produce a complete set of requirements up‑front; in an Agile rollout the BA would work sprint‑by‑sprint, delivering a “minimum viable product” (MVP) and continuously refining the backlog; in a Hybrid rollout the BA might lock‑down the high‑risk regulatory requirements (Waterfall) while iterating on user‑experience enhancements (Agile).

Key Terms & Techniques

Step‑by‑Step / Process Flow

1. Assess Project Delivery Method – Meet the Project Manager (PM) and Scrum Master (if any) to confirm whether the project is Agile, Waterfall, or Hybrid; capture this in the BA Work Plan.
2. Stakeholder Identification & Analysis – Use a stakeholder map (BAPM) to locate decision‑makers, end‑users, and compliance owners; note any “regulatory‑only” stakeholders that may require formal sign‑off (Waterfall).
3. Elicit Requirements – Run a mix of techniques (interviews, workshops, story‑mapping) that fit the delivery style:
4. Agile – focus on User Stories and acceptance criteria.
5. Waterfall – capture Functional & Non‑Functional Requirements in a Requirements Specification.
6. Hybrid – produce both stories for iterative parts and a high‑level Requirements Traceability Matrix (RTM) for regulated components.
7. Validate & Prioritize – Apply MoSCoW or Weighted Scoring; for Agile, ensure each story meets the Definition of Ready; for Waterfall, obtain formal sign‑off via the CCB.
8. Baseline / Commit –
9. Agile – commit the sprint backlog to the team.
10. Waterfall – baseline the Requirements Specification and obtain the Baseline Approval.
11. Hybrid – baseline the regulated portion while keeping the iterative backlog open.
12. Monitor & Adapt – Track progress with burn‑down charts (Agile) or milestone reports (Waterfall); continuously refine backlog items, update the RTM, and report variances to the governance board.

Common Mistakes

Certification Exam Tips

1. Know the Input/Output pairs – Elicitation (input: Stakeholder List, output: Elicitation Results). Exam questions love to swap them; remember the BA elicits information, not the requirements themselves.
2. “What does the BA do next?” – In Agile, after a Sprint Review, the next BA activity is Backlog Refinement; in Waterfall, after a Requirements Review, the next step is Baseline Approval.
3. Hybrid questions often ask you to pick the governance artifact that applies to both worlds – the answer is usually a Hybrid Governance Model or a Combined Phase‑Gate/Iteration Review.
4. Technique‑to‑KA mapping – MoSCoW → Requirements Life Cycle Management; BPMN → Strategy Analysis; DoR/DoD → Solution Evaluation. Memorize these pairings for quick recall.

Quick Check Questions

1. Scenario: After a sprint planning session, the team discovers a story lacks clear acceptance criteria. Which technique should the BA apply?
   Answer: Definition of Ready (DoR) checklist.
   Why: DoR ensures a story is “ready” before a sprint; adding missing acceptance criteria satisfies the DoR.

2. Scenario: A regulated finance client demands a formal sign‑off on all functional requirements before any coding begins. Which artifact must the BA produce?
   Answer: Requirements Specification with a Change Control Board (CCB) process.
   Why: Waterfall‑type regulatory work requires a baseline document and formal change control.

3. Scenario: Stakeholders are split on feature priority. The BA needs a quick, visual way to reach consensus in an Agile sprint. Which technique is most appropriate?
   Answer: MoSCoW Prioritization.
   Why: MoSCoW categorizes items into Must/Should/Could/Won’t, giving the team a shared language for decision‑making.

Last‑Minute Cram Sheet (10 one‑liners)

1. BAPM = planning how the BA works; outputs: Work Plan, Stakeholder Map.
2. Elicitation = activity; Elicitation Results = output (⚠️ not “requirements”).
3. User Story belongs to Requirements Life Cycle Management; it lives in the Product Backlog.
4. DoR = checklist that makes a backlog item ready; DoD = checklist that makes an increment done.
5. MoSCoW = prioritization technique; always paired with Requirements Life Cycle Management.
6. BPMN is a Strategy Analysis tool for “as‑is” and “to‑be” process diagrams.
7. Hybrid Governance Model = mix of Agile ceremonies + Waterfall phase gates; documented in a Governance Matrix.
8. Change Control Board (CCB) only appears in Waterfall (or regulated hybrid) – it approves changes to the baseline.
9. Backlog Grooming = ongoing refinement; the BA updates acceptance criteria, estimates, and priority.
10. Solution Evaluation outputs: Evaluation Report, Recommendations, Updated Requirements (if re‑work is needed).

Good luck – you now have the practical map, the exam traps, and the flash‑facts to ace the BA portion of any IIBA certification!