Category flow

The Busy Kitchen – a parable of work in process

Some software teams get stuck because their business users don’t realise they need to make time to take delivery of features they’ve requested. Over time their UAT backlog increases to the point where the team’s throughput virtually stalls. Once upon a time there was a restaurant. It was a good restaurant with a good reputation. […]

Are we nearly there yet?

The goal of software delivery is to minimise the lead time to business impact. Everything else is detail. The longest journey When I was young our summer holidays usually involved a drive to somewhere on the south coast of England. From where we lived in London this would be a 5 hour journey for a […]

Let your examples flow

Should examples/tests/specs/whatever be DRY(Don’t Repeat Yourself)? I’ve been thinking (and talking and arguing) about the value of test names recently and whether they are just unnecessary duplication, but that’s the subject of a future discussion. This is about the actual content of your examples. So, should your examples be DRY? In a word, no. DRY […]