Deliver a release
- Status
- Review
- Version
- 0.1.2
- Authority
- UASK standard
- Applies to
- Core
Summary
This playbook runs one release, or one significant change, through the three phases that repeat in a project’s life: Spec, Build and Release. It does not restate their parts. The release spec says what the release does and fixes its appetite; the work-packages item says how each piece is built and verified; the quality and release playbook says how the result reaches production. This playbook is the order between them, the gates where the lead or the owner decides, the circuit breaker that stops a release from growing, and the close-out that leaves a record and a number. A fix runs only its short path.
Rules
- R1. Every release or change of the class change or system change (
process.project-lifecycle#R10) MUST run the five stages below in order. A fix MUST run stages 3 and 4 with the plan of the fix in place of a release spec (process.release-spec#R1), and a system change MUST go back to the Blueprint before stage 1. - R2. The release MUST start from a bet: a stated appetite, which is the time the owner will give, set before the design (
process.project-lifecycle#R4). The appetite is fixed and the scope bends: when the work does not fit, the lead MUST cut scope and not extend the time without the owner. - R3. Gate G2 MUST be passed before Build: the lead decides that the release is ready against the Definition of Ready (
process.definition-of-ready), or the owner decides when the release spec changes the scope or the appetite or needs an owner-level decision (process.project-lifecycle#R6). - R4. Build MUST proceed by work packages (
process.work-packages). The lead MUST compare the time spent with the appetite at half of it and again before the release, and MUST say in the log where the release stands: done, in progress, cut, at risk. - R5. When the appetite is reached with the work unfinished, the lead MUST stop and put the options and a default to the owner (
process.release-spec#R12). The default MUST be to ship what is done and to cut the rest, not to extend. An extension is a new bet and MUST be the owner’s decision (mgmt.roles-and-decision-rights#R9). - R6. A change of scope or appetite after approval MUST be a new revision of the release spec and MUST be approved again (
process.release-spec#R15). Work outside the approved packages MUST NOT be merged under the release. - R7. The release itself MUST follow
quality.quality-release: version, changelog, release candidate, staging check, approval against the checklist, backup, deploy, verification and, where needed, rollback or hotfix. Going live with production of a live or client system, and any irreversible step, MUST have the owner’s approval unless a standing rule names the action (process.project-lifecycle#R8). - R8. The first release of a new system MUST pass the hand-over review before Support takes it over (
ops.production-readiness-and-handover). Each later release MUST check the lines its changes touch: the runbook, the versions, the service levels, the access list. - R9. A release to a live service SHOULD reach a limited audience first when the platform allows it (a staging preview, the owner, a share of traffic), with what is looked for and what was learned recorded, before it reaches everyone.
- R10. The release MUST be closed: the release spec ends with a link to the release record and a line that compares the actual effort with the appetite (
process.release-spec#R17), the delivery metrics of the release are written down (mgmt.delivery-metrics#R8), and each incident of the observation period has its record or postmortem (ops.incidents-and-postmortems#R8). - R11. Each phase MUST open with a recall step and close with a record step (
process.project-lifecycle#R13): stage 1 looks for earlier releases of the same kind, and stage 5 writes down what this one decided and learned and where each lesson goes. - R12. The agent that builds a package MUST NOT approve the release, take gate G3 or decide a scope or appetite change; those stay with the roles that
mgmt.roles-and-decision-rightsnames.
Stages
| # | Stage | Artefact | Gate | Who decides |
|---|---|---|---|---|
| 1 | Frame the release | release spec draft with appetite | — | lead drafts, owner confirms the bet |
| 2 | Gate G2: ready | approved release spec, briefs for the first packages | G2 | lead; owner if scope or appetite changes |
| 3 | Build | merged work packages, progress log | package merge gate | lead and the automated gate |
| 4 | Release | release record, verified deployment | G3 for a live or client system | owner, or under a standing rule |
| 5 | Close and record | closed release spec, metrics, lessons | — | lead |
1. Frame the release
- Entry. The owner has chosen the work for the next release, or an item in Support has been classed as a change (
process.project-lifecycle#R10). - Do. Start with the recall step (R11): earlier releases of the same kind, their appetite and actual effort, and open findings. Write the release spec from
templates/release-spec.md(process.release-spec), with the appetite the owner has set, the goals and non-goals, the checks to add first, the rollout and rollback, and the work packages with their estimates. Compare the sum of the estimates with the appetite and cut scope until it fits. - Outputs. The release spec in draft, with the appetite and the tier (
mgmt.governance-tiers). - Exit. The spec has every section its tier requires, the estimates fit the appetite, and every open question has a default (
process.release-spec#R13).
2. Gate G2: ready
- Entry. The release spec is in draft.
- Do. Check the release lines of the Definition of Ready (
process.definition-of-ready#R1toprocess.definition-of-ready#R3). Approve the spec as the lead, or put it to the owner when R3 says so. Write the briefs for the first packages and check each against the package lines of the Definition of Ready. - Outputs. The approved release spec; briefs for the first packages.
- Exit. The release spec is approved and recorded with its date; the first packages are ready (R3).
3. Build
- Entry. Gate G2 passed.
- Do. Take the packages in the order that gives value early. For each: brief, branch, checks first, verifier, merge gate, log line (
process.work-packages). At half of the appetite run the comparison of R4 and cut scope if the release is behind. When a package turns out to need an owner-level decision, stop it and ask (mgmt.roles-and-decision-rights#R12). - Outputs. Merged packages with their evidence; the progress log; a changed release spec where scope was cut (R6).
- Exit. Every package in scope is merged, cut or moved to the next release with a reason; the gate is green on the main branch; or the appetite is reached and R5 has been applied.
4. Release
- Entry. Build is closed and the main branch holds what should ship.
- Do. Run stages 3 to 6 of
quality.quality-release, with the checklist oftemplates/release-checklist.md. For a first release, run the hand-over review (R8) before it. For a live or client system, ask the owner for gate G3 with the checklist, the backup that was proved by restore and the rollback. Reach a limited audience first where R9 applies, then everyone. - Outputs. The release record, the verification results, the hand-over record where R8 applies.
- Exit. The release is verified in production, or rolled back as planned; the observation period is over.
5. Close and record
- Entry. The observation period is over.
- Do. Close the release spec with the link to the release record and the comparison of effort with appetite (R10). Compute the delivery metrics of the release. Write one record of what was decided and learned and where each lesson goes: a change to the Definition of Ready or of Done, a new check, a Hub proposal, a decision for the owner. Open a postmortem for each incident that met the criteria. Say what is left for the next release.
- Outputs. The closed release spec, the metrics, the record, and the list for the next release.
- Exit. The release spec is closed; every lesson names where it goes; the next release has its starting list.
Guidance
When to use
For each release and for every significant change to a running system. For a fix, run only stages 3 and 4. Do not use it for the foundation of a new product, which mgmt.project-foundation runs. A project that has only ever had one
release still uses it, because the first release is where the hand-over is checked (R8).
Tailoring by tier
At the lightweight tier the release spec is a page, the lead decides G2, and the builder checks its own packages against the Definition of Done. At the standard tier the whole playbook applies, with a verifier who did not build each package. At
the high-assurance tier add a second reviewer for each release and a rehearsed rollback (mgmt.governance-tiers#R8). The owner’s gates stay at every tier.
Client projects
A client’s terms of reference stay an input to the release spec, not a substitute for it. The client approves the look and the scope through the owner and does not instruct agents (mgmt.roles-and-decision-rights#R7). The release record
and the hand-over documents reach the client through the owner.
Working with agents
An agent can frame the release, write the briefs, build and verify packages (a different session verifies) and prepare the release. It stops at the gates the roles item reserves. Give a package one brief file and ask for a short report with the commit and the check output. Ask the verifier to work from the diff and the checks, without the builder’s reasoning.
Common mistakes
- Starting to build before the release spec is approved because “the change is small”: take the class seriously (
process.project-lifecycle#R10). - Extending the time instead of cutting scope when the half-way check shows the release behind.
- Merging work that is not in an approved package.
- Releasing a live system on a Friday evening with nobody available to roll back.
- Closing the release without comparing the effort with the appetite, so the next estimate has no data.
Explanation
Why an appetite. Shape Up sets the time first and lets the design fit it: an appetite starts from a number and ends with a design, where an estimate starts with a design and ends with a number. That is what lets the owner buy a release, rather than an open-ended piece of work. Why a circuit breaker. The same book’s policy is that work that is not finished in the time bet does not get an extension by default; the risk of losing a release is what keeps scope honest. Why a limited audience first. GOV.UK describes a private beta, with a limited number of people, to get feedback and improve before the service is run at scale; for a live shop a staging preview or a small share of traffic does the same job. Why a thin playbook. The parts have homes: the release spec, the work packages and the quality playbook. A third place that restated them would drift; this one holds the order, the gates and the close.
Examples
Good. A small UK shop, release RS-004 “delivery dates in order emails”, appetite three agent-days, standard tier. The lead looks up the two earlier mail releases (recall), writes the spec with three packages of one agent-day each and a cut list (the second language), and gets the owner’s confirmation of the bet. G2 passes on the lead’s decision. At half the appetite WP-1 is merged and WP-2 is half done; the lead notes “on course”. WP-3 turns out to need a change to the checkout, which is not in the spec: the lead stops, the owner decides to move it to the next release. The release goes through the quality playbook, the owner approves G3 for the live shop, a share of orders gets the new email first, and the record shows 2.7 agent-days against three. The close-out names one lesson: the brief template needs a line for mail templates.
Bad. “Make the emails nicer”, no spec, no appetite. The work grows for two weeks, the checkout is changed on the way, the owner is asked on the last day whether it can go live, nothing says what was cut and nothing says how long it should have taken. The release has no record, and the next estimate starts from nothing.
Sources
- Ryan Singer, Shape Up, chapter 3 Set Boundaries — Basecamp, all rights reserved; appetite as fixed time and variable scope, summarised, not copied. Accessed 2026-11-21.
- Ryan Singer, Shape Up, chapter 8 Place Your Bets — Basecamp, all rights reserved; the circuit breaker, summarised, not copied. Accessed 2026-11-21.
- GOV.UK Service Manual, How the beta phase works — Open Government Licence v3.0; a limited audience first, then at scale. Accessed 2026-11-21.
- ISO/IEC/IEEE 12207:2017 (software life cycle processes) — referenced by name only.