A long time ago I read a book called the IDEAL problem solver. One thing that stuck from that book was that if you are trying to learn something it is not enough to get a feeling that ‘yes, this makes sense.’
It is often the same thing with requirements. When you write down a requirement or discuss it with the customer it can seem to be clear and make sense. But ‘making sense’ is not always enough. Requirements are often meant to be implemented in a computer with very little room for ambiguity.
We do not want to overspend on detailled requirements long before we need them. Instead we want to specify them as late as possible. We want to keep a DEEP backlog.
So how do we do that? I will write more about this in a while.
