Skip to content

How we work

Still being settled

The team note behind this page is a draft — two of its six sections have not been written, and the rest has not been formally agreed. Read it as how we intend to work rather than a settled contract. The notice comes off when the note does.

How this team decides, reviews and tracks work — written down so nobody has to guess, and so a new joiner is useful on day two instead of week two.

Decisions

Not every decision needs a meeting, and not every decision needs a document. Which one it needs depends on how hard it is to undo:

Kind of decision Who decides How it is recorded
Reversible, local Whoever is doing the work Nothing, or a line in the ticket
Reversible, but it affects others The person, after asking Ticket notes
Hard to reverse The group An ADR in 30-decisions/

If you find yourself re-arguing something, it needed an ADR and did not get one.

Design before code

A design note reaches agreed before tickets are written against it. agreed means build this; current means this is what exists. They are not the same thing, and treating them as the same is how documentation rots.

Work tracking

  • The ticket is the source of truth. The board is a view of it.
  • A card is one link and nothing else.
  • The lane a ticket sits in is what says its status.
  • A ticket is one to three days of work. Anything bigger is an epic that has not been split yet.
  • Every ticket has an owner, acceptance criteria, and a list of what is out of scope.

The lanes

Lane Enters when Leaves when
Backlog It exists, linked to a design note Prioritised and startable
Todo Dependencies are done and it has an owner The owner starts it
In progress Someone is actively on it The criteria are all checked
Review Criteria checked, change open Approved
Blocked The blocker is named in the ticket The blocker clears
Done Merged and demonstrable —

This is Kanban. The work-in-progress limit is the part that matters: the lanes only tell the truth if you are not carrying ten things at once.

Definition of done

A ticket is done when all of this is true, not when the code merged:

  • Acceptance criteria all met
  • Reviewed by someone who did not write it
  • The design note updated if reality diverged from the plan
  • No new decisions left undocumented

Not settled yet

Review norms, and working agreements like overlap hours and response times, are still being filled in. When they exist they will live here rather than in someone's head — this page is written to be the place you look first.

Next: Use the PSN apps