Henry Kobutra
← All notes
Companion material

acceptance template

Task and acceptance record

Before work

  • Outcome, stated as observable behavior:
  • In scope (paths and behavior):
  • Out of scope:
  • Allowed actions:
  • Actions requiring separate approval:
  • Authoritative requirement or decision:
  • Starting revision and any existing local changes:
Criterion Input or scenario Expected result Check
Reported defect
Nearby behavior
Failure or boundary case

At handoff

  • Changed files and reason:
  • Exact tested revision, or retained snapshot and local diff:
  • Runtime, dependencies and relevant configuration:
  • Commands, exit codes and evidence location:
  • Observed result for each criterion:
  • Unchecked criteria and why:
  • Review findings and fix verification:
  • Decision: accept / return for correction / hold for missing evidence
  • Acceptor and authority, recorded by the person who accepts:

Passing checks do not grant permission to merge, publish or change production.

A conversation starts somewhere

What are you
working on?

If something here connects with what you're working on, email me.

henry@kobutra.com