| Variable | Predictive (Waterfall) | Adaptive (Agile) | Hybrid (RUP/SAFe) | | :--- | :--- | :--- | :--- | | | High (well-understood problem) | Low (evolving problem) | Medium (some known, some unknown) | | Regulatory Pressure | High (audit trails needed) | Low | Medium | | Team Size | Small or Very Large | Small (<12 people) | Large (>50 people) | | Cost of Change | High (physical/hardware) | Low (software) | Medium | | Business Stability | Static | Dynamic | Fluctuating |
: Visualizes the flow of work across different departments using tools like Visio , Miro , or Lucidchart . business analyst methodologies
A mature BA does not ask, "Which methodology is right?" but rather, "Which methodology is right for this project, at this time, in this culture ?" They understand that: | Variable | Predictive (Waterfall) | Adaptive (Agile)
SAFe is the dominant methodology for large enterprises (100+ people) trying to do Agile. It layers Agile teams (Scrum/Kanban) onto a predictive program and portfolio level. While the fundamental goal of a BA remains
While the fundamental goal of a BA remains constant—delivering value and solving problems—the approach varies significantly depending on the project environment. This write-up explores the two dominant methodology categories (Waterfall and Agile), as well as specialized approaches used to tackle specific business challenges.