SELF-GUIDED BA PRACTICE Packages available · Access after confirmed paymentSee packages ↗

Business analysis glossary

Assumption

What it is

An assumption is something the team believes to be true for planning purposes but has not yet proved. Assumptions are recorded so they can be checked, because if one turns out to be false, plans, estimates or requirements may need to change. They usually sit in a RAID log next to risks, issues and dependencies.

Why it matters

Hidden assumptions are a common cause of project surprises. Writing them down turns silent guesses into items someone owns and verifies. An analyst who says 'we assume the payment provider supports refunds through its API' gives the team a chance to confirm it before stories are built around it.

Example

During planning at Monsoon Mart, the analyst records three assumptions: the courier partner shares tracking updates through a webhook, store staff have smartphones and existing customer addresses are mostly valid. The second one proves false at two rural stores, so tablets are added to the budget before the rollout.

CHECK BEFORE CONTINUING

Keep your work safe