I know what you’re thinking: Can’t I just Google these techniques?
You might be thinking: Do I really need 123 different ways to analyze a business? I know what you’re thinking: Can’t I just
The truth is, the difference between a good BA and a great BA is the size of their toolkit. A handyman with only a hammer sees every problem as a nail. A BA with only a few techniques sees every project as a generic checklist. A handyman with only a hammer sees every problem as a nail
[]
The result? We discovered that 80% of the delays were caused by just 2 out of 20 stakeholders not validating their assumptions. We fixed the communication flow. Without this specific set of techniques, we would have kept arguing about the software, not the process. We discovered that 80% of the delays were
is not just a collection of definitions. It is a battle-tested framework for delivering clarity out of chaos.
You know you need to elicit requirements. You know you need to bridge the gap between the stakeholders and the developers. But when you sit down to start the work—which tool do you pull out? Do you run a SWOT? A MOST analysis? A Catwoe? A Process Flow? Or do you just default to the same three techniques you’ve used for the last five years?