liveBook · Manning

Checklist

As explained in Build High Value Software Systems

A list of items or steps that can be checked to support consistent completion of a task or process.

A checklist is a written sequence of checks for completing a recurring task consistently. It makes personal routines auditable and less dependent on memory, especially under pressure. Before a staging deployment caused errors, Evelyn skipped a manual configuration check; writing it down would have caught the problem. section 14.2

Keep a checklist useful by treating it as a living record of risks:

  • Add specific checks after your own mistakes, team incidents, or lessons from others. section 14.2.1
  • Remove manual checks when automation enforces them; a checklist that only grows can become noise. section 14.2.1
  • Mark checks that should be automated, so the checklist can guide improvements to CI or deployment procedures. section 14.2
Listing 14.2 Pre-deployment standard work checklist
# deploy-checklist.yml
pre_deployment:
  - verify_config:
      check: "DB_HOST matches staging endpoint"
      how: "diff .env.staging against known-good config"
      automated: false   # TODO: add CI check
  - verify_migrations:
      check: "All pending migrations applied to staging DB"
      how: "run: python manage.py showmigrations --plan"
  - verify_tests:
      check: "All tests pass on this commit"
      how: "check CI status badge on the PR"
  - verify_secrets:
      check: "No hardcoded credentials in diff"
      how: "run: git diff HEAD~1 | grep -i 'password\|secret\|key'"
  - verify_rollback:
      check: "Previous deployment tag is recorded"
      how: "note current deployed commit SHA before deploying"

A pre-deployment checklist makes each check actionable by specifying what to verify and how. section 14.2

How Build High Value Software Systems covers it

How deep it goes
Explains checklist creation from failures, item removal, and progression toward automation through deployment examples.
Examples
Uses pre-deployment checks for configuration, migrations, tests, secrets, rollback, and cache warm-up.
What you can do after
Apply checklists by encoding failures as specific checks, then removing manual checks when automation enforces them.
How it connects
Connects checklists to standard work, continuous improvement, incident reviews, and CI automation.

Also explained in

Compare how 5 books explain checklist →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.