Two people describe the same requirement, both sound right, and the built
thing satisfies neither. It traces back to one word meaning two things. This
is not vague requirements. It is unshared meaning, and here is how a BA finds
the load-bearing terms, pins them, and keeps them current.
Your engagement time keeps landing on the loudest people while a quiet, high-influence stakeholder gets missed until it hurts. Stakeholder analysis is how a BA maps who actually matters, and why, then puts engagement where it changes the outcome.
Gap analysis for BAs, explained without the strategy jargon. Compare current state to target state, list what your project is missing, and turn each gap into work before it surfaces in UAT.
Process maps have a habit of ballooning until nobody reads them, or pulling you so deep into one branch you lose the whole process. The fix is to map at a deliberate level of detail: decide the one question the map must answer, map the happy path first, add only the exceptions that matter, and stop there. A practical guide for BAs who want maps that stay useful.
Definition of Ready and Definition of Done are not Agile ceremony — they are two lightweight quality gates that bracket the BA's work on every story. This guide explains what each one does, why they solve different problems, and how a BA shapes and uses both on a real project.
Most acceptance criteria confirm the feature exists. They do not describe how it behaves and UAT finds out the difference. This guide shows how to write criteria that make expected business behavior explicit before the build starts.