The Better Business Analysis Delivery Journey
The Better Business Analysis Delivery Journey
The 7-phase model that describes how a BA engagement unfolds — from strategic context through to post-release improvement.
Enterprise & Strategy Analysis
Understand the organisation's goals and strategic context before any requirements work begins.
Problem Analysis & Definition
Define the real problem — its root cause, scope, and business objectives. Not the presenting symptom.
Processes & Solution Scope
Map current processes (as-is), design the future state (to-be), and agree the project scope.
High Level Requirements
Translate business needs into epics and capability statements — the broad strokes of what will be built.
Detailed Requirements Analysis
Specify the functional and non-functional requirements in detail — user stories, acceptance criteria, data models.
Delivery & Requirements Management
Support the build: managing changes, maintaining traceability, resolving queries, and tracking defects.
Release & Operational Improvement
Support go-live and capture lessons learned. Monitor whether the delivered solution delivers the expected value.
💡 In practice: You will rarely start at Phase 1. Most BAs are engaged mid-project. The first thing you do — wherever you enter — is assess which phase the project is in and create your Agile BA Plan.
📌 Key Points
The 7 phases: Enterprise Analysis → Problem Definition → Processes & Scope → High Level Reqs → Detailed Reqs → Delivery → Release
Most BAs are not engaged at Phase 1 — assess where the project is before starting any analysis work
The Delivery Journey is a mental model, not a rigid process — in Agile, you iterate between phases
Each phase produces a tangible output — not just a set of meetings. Know what your deliverable is at each step
Connect the Delivery Journey to a project you know
The 7-phase Delivery Journey describes how BA work flows through a project. It's much easier to remember when you anchor it to something real.