← Expertise
Software Development
We design software around observable behaviour. A small end-to-end slice gives the team a place to test domain language, persistence and the consequences of interrupted work.
Design question
Which behaviour must survive a change?
Capture the invariant
State a rule in terms a domain expert can check. For a reservation, that might be the point after which the last available place cannot be promised twice.
Exercise the interruption
Test a failure between the write and its acknowledgement. Decide whether a retry should resume, return an existing result or ask for a fresh decision.
Leave a readable release
Keep the change set narrow. Record the evidence that supports release and the signals that would send the team back to the previous version.
A working increment, executable examples and a release note that explains the behaviour change.
Prepare your brief