I find the idea about describing the requirements to the computer leading to greater human understanding of the requirements interesting. Where I work, the product people decide random shit on a whim so this would be deemed &quot;not Agile&quot;, but insightful nonetheless.<p>I have actually used Cucumber before, back when it was a new thing. It was mostly a boondoggle because this was a .NET shop, so our QA folks would figure out how they wanted their Cucumber tests to look (may have been Gherkin, not clear on the distinction), then the .NET devs would have to go off and write Cucumber parsers for that, then the tests could be run. You can imagine this cycle taking roughly forever. (&quot;parser&quot; is probably the wrong word, but, the thing that takes a bunch of English words, turns them into code, then evaluates it)