Delivery & governance consultancy · registered in KentMon–Fri 09:00–18:00 UK timesecops@redbackdelivery.bid
Talk to us

Redback · Field notes on software delivery

Field notes

Short, practical notes from the work. Take what is useful.

Illustrative image: brick arches and a cherry-red glass door

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.

2. Release often enough that it becomes boring

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.

3. How to read an amber status report

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.

4. Supplier meetings that end in decisions

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.

5. Contingency is not padding

Hold contingency explicitly, at programme level, with a named person who can release it. Hidden padding in every estimate disappears; visible contingency is managed.

6. Plan the handover to support on day one

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.