Project brief
Problem statement, objectives, scope and explicit out-of-scope, ready to circulate.
DEFINE
The professional outputs a consultant actually gets paid for.
The project state is rendered into a focused set of accepted deliverables rather than an exhaustive list of formats. Requirements, scope, decisions, open issues and the process flow are generated from maintained state, so they never drift from what the project actually agreed.
OUTPUT PACKAccepted Deliverables
traceable to stateBriefproblem & scopeRequirementswith acceptance criteriaIssues & decisionsstate + ownerProcess flowas-is / to-be
Project stateProject StateAccepted outputs
016
Outputs in the initial pack
02Traceable
Every requirement to evidence
03Current
Regenerated from state
CAPABILITIES
What this stage of discovery actually does.
Built for this stage
of project discovery.
Each capability moves the project state closer to something a client can accept and a delivery team can start from.
CAPABILITIES04
STAGEDEFINE
Requirements and scope table
Business, functional and non-functional requirements with acceptance criteria attached.
Open issues and decisions
A decision log and open-issue list, each entry carrying its current state and owner.
Process flow and readiness report
As-is and to-be process flows, plus the discovery readiness position behind them.
HOW IT WORKS
How this stage works.
01
State is read
Deliverables are generated from maintained project state, not from a transcript.
02
Traceability applied
Each requirement points back to the evidence that established it.
03
Accepted
Outputs go to the stakeholders who have to accept them.