Delivery is a controlled path, not a staffing arrangement.

Each phase has entrance criteria, exit criteria, and artifacts. If those are missing, the program is not ready to move—even if the slides are green.

Lifecycle with real gates

01
Discovery
Next → Architecture
Entrance
A named problem, sponsor, and access to the people who own the current process.
Exit
Agreed problem statement, constraints, and a decision on whether to proceed.
Artifacts
- Situation assessment
- Stakeholder map
- Risk hypotheses
02
Architecture
Next → Plan
Entrance
Discovery complete, constraints documented, architecture authority identified.
Exit
Target-state options, a recommended path, and recorded decisions.
Artifacts
- Architecture options
- ADR
- Integration sketch
03
Plan
Next → Build
Entrance
Architecture direction accepted. Commercial and delivery model agreed.
Exit
Backbone plan, RAID baseline, quality approach, and governance calendar.
Artifacts
- Program plan
- RAID log
- QA strategy
04
Build
Next → Validate
Entrance
Plan and environments ready. Definition of done in force.
Exit
Increments that meet agreed quality evidence, not just demo criteria.
Artifacts
- Working software / models
- Test evidence
- Status pack
05
Validate
Next → Deploy & operate
Entrance
Build increments complete enough for operational and user validation.
Exit
UAT evidence, defect disposition, and a go/no-go recommendation.
Artifacts
- UAT pack
- Defect log
- Release gate
06
Deploy & operate
Entrance
Release gate passed. Support, access, and rollback understood.
Exit
Production in agreed service bounds, knowledge transferred, residual work listed.
Artifacts
- Release record
- Operating handbook
- Handover register

Engagement model

How an engagement actually starts.

Beginning

We start with the initiative, the constraint, and the stakeholders who can decide. Commercial shape follows the work: a defined discovery, a program with gates, or support to an existing client team. We do not lead with “augmentation” as the brand.

Named ownership

Programs have named leads. Continuity matters more than rotating a bench. Where a specialist is required for a bounded period, that is explicit in the plan—not a surprise substitution.

Handover

Operate is a phase with artifacts: runbooks, residual RAID, access revocation, and knowledge transfer. If those are missing, the program is not finished.

Go deeper

Governance & program controlsSteering, decision rights, RAID, change, and reporting.Read →Quality assuranceDefinition of done, reviews, testing, and release gates.Read →Security & complianceAccess, SDLC, data handling, and vendor assessment.Read →

Next step

Ask how the first ninety days would be governed.

If we cannot describe steering, RAID, and quality evidence, we are not ready to staff a team.

Discuss an initiative

Lifecycle with real gates

Discovery

Next → Architecture

Entrance

A named problem, sponsor, and access to the people who own the current process.

Exit

Agreed problem statement, constraints, and a decision on whether to proceed.

Artifacts

Situation assessment
Stakeholder map
Risk hypotheses

Architecture

Next → Plan

Entrance

Discovery complete, constraints documented, architecture authority identified.

Exit

Target-state options, a recommended path, and recorded decisions.

Artifacts

Architecture options
ADR
Integration sketch

Plan

Next → Build

Entrance

Architecture direction accepted. Commercial and delivery model agreed.

Exit

Backbone plan, RAID baseline, quality approach, and governance calendar.

Artifacts

Program plan
RAID log
QA strategy

Build

Next → Validate

Entrance

Plan and environments ready. Definition of done in force.

Exit

Increments that meet agreed quality evidence, not just demo criteria.

Artifacts

Working software / models
Test evidence
Status pack

Validate

Next → Deploy & operate

Entrance

Build increments complete enough for operational and user validation.

Exit

UAT evidence, defect disposition, and a go/no-go recommendation.

Artifacts

UAT pack
Defect log
Release gate

Deploy & operate

Entrance

Release gate passed. Support, access, and rollback understood.

Exit

Production in agreed service bounds, knowledge transferred, residual work listed.

Artifacts

Release record
Operating handbook
Handover register

How an engagement actually starts.

Beginning

Named ownership

Programs have named leads. Continuity matters more than rotating a bench. Where a specialist is required for a bounded period, that is explicit in the plan—not a surprise substitution.

Handover

Operate is a phase with artifacts: runbooks, residual RAID, access revocation, and knowledge transfer. If those are missing, the program is not finished.