BVDLC's Three Pillars explain why delivery works differently in the AI era. The Six Phases explain what to do and when. The Delivery Model explains who does it and how — the team shape, the shared context, and the working cadence that turn the method into a real production team.
The delivery model rests on four things. Miss any one, and the other three stop working.
Business intent, domain rules, and design decisions live as Markdown in the repository — versioned, reviewed, and read by every agent session. No tribal knowledge. No out-of-date wiki.
Four roles hold the model together: Context Manager, Engineering Practice Lead, Squad Lead, and Squad Engineer. Each one owns a specific kind of decision that agents cannot make.
Work runs inside small teams of humans and agents — a senior engineer plus a handful of mid-level engineers, running concurrent agent sessions against a shared spec.
Every feature follows the six BVDLC phases through fourteen concrete steps, with four sign-off points where a human decision moves the work forward: intent approved, idea validated, spec locked, verified for release.
Three columns. Roles that make the decisions. Artifacts that carry the context. A cadence that moves work from first signal to measured value.
Five non-negotiable principles. If any is violated, the model breaks down into the same AI chaos it was built to prevent.
Traditional titles (PM, tech lead, engineer, QA) still exist. The delivery model adds four roles on top — the roles that make a human-agent team actually work.
Owns the shared context. Maintains it, unblocks teams, captures improvements, and coaches. Makes the shared context smarter every week.
See the playbook →Directs agents on the hardest work. Maintains code patterns. Coaches engineers on when to let an agent run and when to stop it.
See the playbook →Runs one delivery squad. Reviews agent PRs against spec intent. Owns end-to-end delivery of a feature area.
See the squad pattern →Runs concurrent agent sessions. Feeds them context, reviews their output, writes the integration tests agents struggle with.
See the squad pattern →Each page below goes one level deeper. Start with the workflow if you want to see how work flows; start with the squad page if you’re shaping the team.
Fourteen steps through the six phases, from first signal to measured value. Four sign-off points. Owner and artifact per step.
Walk the workflow → Team shapeHow a squad is structured, how a day and week run, and the decision split between humans and agents.
See the squad → RoleThe four parts of the job — maintain, unblock, improve, coach. Sample week. Starter metrics.
Open the playbook → RoleThe three parts of the job — build, standards, coach. Plus the skill of knowing when to stop an agent.
Open the playbook → ComplementThe per-feature Phase 0–5 scaffold that keeps each feature’s context organized from business intent to monitoring.
See the folders →