Skip to content

Draft — not approved. A working draft by UASK. It may change without notice.

Definition of Ready

Status
Review
Version
0.1.1
Authority
UASK standard
Applies to
Core
Markdown source

Summary

This is the only Definition of Ready of the Hub. A release is ready for Build at gate G2 when its lines R1 to R3 are true; each work package is ready when R4 to R11 are true. An item that fails a line is clarified, split or marked blocked before anyone starts it. The list is a tool for picking work, not a form to fill in for its own sake. A project copies it from templates/definition-of-ready.md, adds its own lines and does not remove any.

Rules

The release (gate G2)

  • R1. The release spec MUST be approved by the lead, or by the owner when it changes the scope or the appetite or needs an owner-level decision (process.project-lifecycle#R6).
  • R2. The appetite MUST be stated with what is left out if it is reached, and the sum of the package estimates MUST NOT exceed it.
  • R3. The rollback MUST be written before the work starts, and for a live system the backup proved by restore MUST be named (process.project-lifecycle#R11, quality.quality-release#R13, process.release-spec#R10).

Each work package

  • R4. The goal and the expected outcome MUST be stated in the user’s terms, not as a solution, and MUST cite the requirement ids or the issue the package serves.
  • R5. The Done criterion MUST name the method, the environment, the expected result and who performs it, and MUST be possible to perform where it says (req.acceptance-criteria#R2).
  • R6. The package MUST fit one builder, one branch and one pull request, and its estimate MUST be stated (process.work-packages#R2).
  • R7. The files the package may touch and must not touch MUST be listed, and the checks to write first MUST be named (process.work-packages#R1).
  • R8. The dependencies, access, accounts and test data the package needs MUST be available, or the package MUST be marked blocked.
  • R9. The risk MUST be noted: does it touch stored data, money, security, privacy or a public interface? If it does, the extra checks MUST be named.
  • R10. How the package will be verified MUST be known: the test level and the command that runs it.
  • R11. A decision that only the owner can make MUST be made, or the package MUST be marked blocked (mgmt.roles-and-decision-rights#R9).

The project’s own lines

  • R12. A project MAY add lines for its own product, for example “design approved” or “content supplied by the client”. It MUST NOT remove any line above.

Guidance

Use the list when picking work, one line at a time, and write the answer that fails in the issue. A package that fails R4 is the commonest: the brief says what to build and not what outcome it serves, so nobody can say when it is done. A package that fails R8 is the commonest cause of idle time; check access first, before the estimate is trusted. Where one line does not apply, write “n/a” and the reason in the brief.

The lead applies the list. The lead decides alone unless R1 says the owner does. At the lightweight tier the list is short in practice, since most lines are true by inspection; it is still the same list.

Explanation

Why one list. Two lists, one for the release and one for the package, were kept in different places and drifted. Here the release lines come first and the package lines second, so a project that has no separate release spec (a fix) meets R4 to R11 only. Why “ready” at all. Work started on a vague goal costs most when it is finished and then found to be the wrong thing; the checks here are cheap compared with that. The Agile Alliance describes the Definition of Ready as explicit criteria, generally based on INVEST, that an item meets before it is accepted into an iteration. This list keeps to the facts a builder needs and no more, so that it stays a tool for picking work and does not grow into a gate of its own.

Examples

Good. Release RS-004 of a small UK shop, “delivery dates in order emails”, appetite three agent-days. At G2 the lead finds the spec approved (R1), the packages summing to 2.5 agent-days with the second language left out if the appetite is reached (R2) and a rollback of one revert plus a restore of the mail templates (R3). Package WP-2 passes R4 to R11 apart from R8: the test mailbox is not set up. It is marked blocked, the lead asks for the mailbox, and the package starts next day.

Bad. An issue “improve emails”. It names no outcome (R4), no way to check it (R5), and touches the checkout, which holds payments (R9), and nobody noticed. It is started on a Monday, and on Thursday the owner is asked a question that should have been asked before it began.

Sources