1. Write “done” before you write the plan
A plan built on undefined deliverables measures effort, not progress. For each significant deliverable, write acceptance criteria that a user and a tester would agree on. Then plan.
Redback · Field notes on software delivery
Short, practical notes from the work. Take what is useful.

A plan built on undefined deliverables measures effort, not progress. For each significant deliverable, write acceptance criteria that a user and a tester would agree on. Then plan.
Every release is a rehearsal for the next. Teams that release monthly treat it as an event; teams that release weekly treat it as a routine. Invest in automation and test environments until release day is unremarkable.
Ask three questions: what has been accepted since last time, what is the forecast based on, and what decision do you need from me? If the answers are “not much”, “judgement” and “none”, amber is probably red.
Circulate the decisions needed in advance, with evidence. Keep the attendee list small. Record each decision with its owner and date before the meeting closes.
Hold contingency explicitly, at programme level, with a named person who can release it. Hidden padding in every estimate disappears; visible contingency is managed.
Operations teams inherit what projects build. Involve them in acceptance, agree support documentation as a deliverable, and do not declare success until they are comfortable.