KNOWLEDGE HUB

Business analysis glossary

53 business analysis terms explained in plain English, from acceptance criteria to wireframes. Search, or jump to a letter.

A

A/B testing
Showing two versions of something to similar groups of users and measuring which performs better against an agreed metric. Read more →
Acceptance criteria
The conditions a user story must meet to be accepted as done. They make a requirement testable, often written as Given / When / Then.
Agile
Delivering work in short cycles with frequent feedback, so the plan can change as the team learns. Read more →
As-is (current state)
How a process or system works today, warts and all. You map it before designing the future state.

B

Backlog
The prioritised list of everything the team might build, from big epics to small fixes.
BPMN
Business Process Model and Notation: a standard set of shapes for drawing process maps that everyone can read the same way.
BRD (Business Requirements Document)
Describes what the business needs and why: objectives, scope, stakeholders and high-level requirements, without saying how it will be built.
Business case
The argument for doing a project: the problem, the options, costs, benefits and risks, and a recommendation.

C

Change request
A formal request to change agreed scope, so its impact on time, cost and quality can be assessed before anyone says yes.

D

Data dictionary
A reference listing every field in a dataset: its name, meaning, type, source and rules. It stops people reading the same number in different ways.
Decision table
A table of business rules: each row sets conditions and the outcome when they are met. Business staff can read and change it without touching code. The DMN standard defines how they work.
Definition of Done
The checklist a piece of work must pass before the team calls it finished, such as tested, reviewed and documented.
Definition of Ready
The checklist a user story must meet before it can enter a sprint: a clear user, a reason and testable acceptance criteria.
DPIA (Data Protection Impact Assessment)
A UK GDPR assessment of the privacy risks of a new process or system, carried out before it starts. It is required when processing is likely to be high risk, for example when AI is used on personal data.

E

Elicitation
Drawing out requirements from stakeholders through interviews, workshops, observation, surveys and document analysis.
Epic
A large piece of work that's too big for one sprint, broken down into smaller user stories.

F

Fishbone diagram
A root-cause diagram (also called Ishikawa) that groups possible causes of a problem into categories such as people, process and technology.
Fit-gap analysis
Comparing what a product does out of the box with what the business needs, to decide what to configure, build or change. Read more →
Five whys
Asking 'why?' repeatedly, usually about five times, to get from a symptom to its root cause.
FRD (Functional Requirements Document)
Describes how a system should behave: features, rules, inputs, outputs and edge cases, detailed enough for developers and testers.

G

Gap analysis
Comparing the current state with the desired future state to identify what has to change.

H

Human in the loop
A design where AI or automation makes a suggestion but a person checks it and makes the final decision. Used where mistakes are costly or the law expects human judgement.

K

Kanban
Managing work as a continuous flow on a board, with limits on how much is in progress at once. Read more →
KPI (Key Performance Indicator)
A measurable value that shows whether a process or project is meeting its goals.

M

MoSCoW
A prioritisation technique: Must have, Should have, Could have, Won't have (this time). Read more →
MVP (Minimum Viable Product)
The smallest version of a product that delivers value and lets you learn from real users.

N

Non-functional requirement
How well a system must work rather than what it does: performance, security, availability, accessibility.

O

Options appraisal
Comparing several ways to solve a problem, including doing nothing, against agreed criteria such as cost, risk and benefit, so the recommendation can be justified.

P

Pain point
A specific problem people run into in the current process, such as a delay, re-keying or a missing update. Each one is logged with evidence so it can be traced to a requirement.
PESTEL
Analysing external factors: Political, Economic, Social, Technological, Environmental and Legal. Read more →
Pilot
A small, time-limited trial of a change with real users, measured against agreed success criteria, before deciding whether to roll it out.
Power/interest grid
A 2x2 map of stakeholders by how much influence they have and how interested they are. It shows who to manage closely, keep satisfied, keep informed or monitor.
Problem statement
A short, agreed description of the problem, who it affects, its impact and what a good solution would achieve. It keeps the team focused on the problem rather than a favourite solution.
Process mapping
Drawing the steps, decisions and hand-offs in a process to understand and improve it. Read more →
Product owner
The person in a Scrum team who owns the backlog and decides what gets built next.
Prototype
A working or clickable model of a screen or system, built to test an idea with users before it is fully built. More detailed than a wireframe. Read more →

R

RACI
A matrix showing who is Responsible, Accountable, Consulted and Informed for each task or decision.
Requirements traceability matrix
A table linking each requirement to its source, design and test cases, so nothing is missed or built without a reason.
Root cause analysis
Finding the underlying reason a problem happens, not just its symptoms.

S

Scope creep
Uncontrolled growth in what a project is expected to deliver, usually without more time or budget.
Scrum
An Agile framework that delivers work in fixed sprints, with set roles (product owner, Scrum master, team) and set meetings. Read more →
Sign-off
Formal agreement from stakeholders that requirements or a delivered solution are accepted.
Sprint
A fixed period, usually one to four weeks, in which a Scrum team delivers a set of backlog items.
Stakeholder
Anyone affected by, or able to influence, a project or its outcome.
Stakeholder analysis
Identifying stakeholders and mapping their interest and influence, to plan how to engage each one.
SWOT
Strengths, Weaknesses, Opportunities and Threats: a quick strategic assessment. Read more →

T

To-be (future state)
How a process or system should work after the change.

U

UAT (User Acceptance Testing)
Business users testing a solution in real scenarios before it goes live. Read more →
Use case
A description of how a user interacts with a system to achieve a goal, including alternative and error paths.
User story
A short requirement from the user's point of view: As a [user], I want [goal] so that [reason]. Read more →

W

Waterfall
Delivering in sequential stages, each signed off before the next begins. Read more →
Wireframe
A simple, low-detail sketch of a screen layout used to agree structure before visual design. Read more →
Workshop
A facilitated session where stakeholders work together to elicit, prioritise or agree requirements. Read more →

No matching terms. Try a shorter word.

Want to see these ideas in practice?

My case studies show how I apply them on real projects.

Scroll to Top