Stop 01 · Business Analysis FoundationsTopics · 4/9

The Business Analysis Lifecycle

In short

BA work isn't random meetings. It follows a loop: understand the need, gather and shape requirements, help build it, then check it worked. Knowing where you are in that loop keeps you calm.

A typical flow — identify the business need, elicit and analyze requirements, document and validate them, support design and delivery, then verify the solution actually solved the original problem.

The purple blob waits at a bus stop with a suitcase and a rolled-up trip plan.

Think of it like this

Planning a family trip

First you ask why: rest, or a cousin's function? Then you ask everyone what they want, make a plan, get everyone to agree, book and travel. On the way back you ask, 'Was it worth it?' Same loop, different trip.

Watch it happen

One requirement's trip through the lifecycle

Need

Elicit

Analyse

Validate

Support

Evaluate

1/6A need appears: the loan approval process takes ten days and customers are leaving.

The big ideas

What you need to know

It starts with a need

A problem or an opportunity, stated in business terms. Not 'build a portal', but 'approvals take too long'.

It loops, not a straight line

Evaluation often uncovers new needs, so the cycle starts again. In Agile teams the loop runs every sprint.

The BA stays during the build

Your job doesn't end when the document is signed. Developers and testers will have questions only you can answer.

Success is measured

Agree up front how you'll know it worked, such as approval time, error count or complaints.

Save yourself the pain

Common mistakes

Oops

Disappearing after requirements are signed off.

Do this instead

Stay close to the team during build and testing. Gaps and questions always show up there.

Oops

Skipping evaluation because the feature went live on time.

Do this instead

Go back and measure. On-time delivery of the wrong fix still leaves the problem in place.

Your mission

Map a real change to the lifecycle

~15 min

Quick check

A new feature went live last month. Which lifecycle stage are you in when you check whether it fixed the original problem?

Go deeper

1Sketch a real or hypothetical project through all stages of this lifecycle.
2Identify which stage is most commonly rushed or skipped in real projects.
3Learn why the lifecycle often loops back on itself rather than proceeding linearly.