How We Deliver
This section covers the commercial and delivery half of the lifecycle: turning a lead into a signed engagement, and running it to handover. The code half lives in Engineering Standards; the toolchain half in the Azure DevOps Playbook.
For the whole lifecycle including build, QA, and go-live on one page, see The Whole Picture (SDLC).
The stages
Section titled “The stages”flowchart LR
Lead["Lead"] --> Disc["Discovery & BA"]
Disc --> Est["Estimate"]
Est --> SOW["SOW signed"]
SOW --> Kick["Kickoff"]
Kick --> Build{"Build loop<br/>2-week cadence"}
Build --> Hand["Handover"]
In this section
Section titled “In this section”- Discovery & BA Deliverables — how a raw lead becomes a scoped backlog ready to estimate, and what the BA produces along the way.
- Estimation & Scoping — three-point PERT ranges, never a single fixed number. How we size, pad, price, and sign off.
- Statement of Work (Template) — the fill-in SOW: scope, milestones, pricing, warranty, handover.
- Kickoff Agenda & Exit Criteria — the alignment that must exist before the build starts.
- Delivery Lifecycle — the build loop itself, and the cadence we run it on.
- Communication Cadence — standup, weekly written status, client demo, retro, and blocker escalation. The one source for meeting rules.