The last two geeky conversations I had, stumbled upon the same thing – how do you measure the effectiveness of requirements in describing the business to the business and describing the specification to the developer?
So, I posed the question “How far away are you from executing your requirements?”. If you are going to go through various steps and stages to get to compilation and then execution, then every step is an opportunity for valuable information being lost in translation. If you can compile your requirements immediately then nothing will be lost.
Each additional step between requirements description and compilation and execution is an opportunity to confuse the user and the developer and everyone in between. That’s why fully dressed use cases are not so effective as fully dressed behavior driven stories. And that’s why BDD is very agile and a great asset in DDD and use cases just don’t cut it anymore.
Right now, my favorite tool is Cucumber. I can execute the requirements and that raises the clarity ranking of my requirements super high.
One thought on “Measuring the Clarity of Requirements”
Thanks Aslam! I read the BDD article you mention, and it has definitely shed more light on the little understanding I had of BDD!