It started with friends

A few of our friends work in robotics. Over dinners and board games they kept telling us about projects that went wrong near the end, over something everyone thought was agreed.

So we asked around. What we kept hearing was that requirements matter more than anything else in a project, and that they get skipped because the work is tedious.

We're trying to make it less tedious.

Three things we're stubborn about

A requirement is only worth building from when it has all three. Turn one off and see what you are left with.

What you haveA requirement that holds up at FAT

Pallet size 1200 × 1000 mm

Source
Said on the kickoff call, 04:12
No source. Now it is your memory against theirs.
Customer
Confirmed by the customer
Not confirmed. Everyone is confident and nobody checked.
History
Unchanged since kickoff
No history. It changed in week twelve and nobody wrote that down either.

Turn one off and see what happens.

All three off. This is how most requirements live today.

Got a project you're still annoyed about?

Tell us about it. We find this stuff interesting, which is how we ended up here. We will mention what we are building (briefly). Everyone leaves feeling a little better.