Great article from David about “evolutionary architecture” and a nice example about it from the Microsoft Word ribbon.

David explains desirements and requirements as:

A desirement is a non-compiled request for software to change. Examples include specification documents, Team Foundation Server Work Items, index cards, and hope expressed with Microsoft Word.

Everyone can state a desirement and throw it on the bottom of the wishlist.
The interesting part is when a desirement gets closer to be a requirement (bubbles up) and the team discusses about the details and writes acceptance tests with the business to confirm them. 

A requirement, on the other hand, is an automated test proving desired behavior exists in software. Requirements (tests) must pass before software may ship.

This leads to creating a ATDD Ready Backlog, which is a great way to make sure you have “always releasable software”.

Full article from David Starr:
http://visualstudiomagazine.com/articles/2013/01/07/leveling-up-agile-requirements.aspx

Great explanation from fellow trainer Ralph Jocham about ATDD + Scrum, where he explains how to approach testing in Scrum with the goal to have a “ATDD Ready Sprint Backlog”

This is one of the topics ATM that I am most excited about

BTW: Steve Freeman has exactly done this with an XP team in London
My recap 

Sustaining an XP team over 7 years
http://gfader.tumblr.com/post/19004526097/qconlondon-recap-sustaining-an-xp-team-over-7-years  

Ralhp’s article here
Creating an ATDD Ready Sprint Backlog in Scrum http://www.methodsandtools.com/archive/atddreadysprintbacklog.php

Best part

ATDD isn’t about a tool like FitNesse, Cucumber, or Robot Framework. ATDD is about making sure that your development team develops the right product

What I was missing in that article is

#1 “Gherkin” as a DSL that helps discuss a specification between shareholders, business people and developers

#2 Distinction between Feature and Scenarios

Getting Started with ATDD: Overcoming the Biggest Mistakes Right from the Start
http://www.informit.com/articles/article.aspx?p=1905549

Don steps through Unit-Testing, TDD and BDD to help us write maintainable high-quality code.
Who doesn’t want that? 

Questions to consider:

• Should you test private methods?
• Should you test every getter/setter?
• What changes when you call your tests, “behaviours”?

Find the recording and many more on the Scrum.org webcast website

Adopting Test-First Development with Don McGreal
http://www.scrum.org/webcast

Great article with the history behind of BDD and the “differences” between ATDD and BDD.

A great statement can be found in the comments:

I also conclude in that video that the difference doesn’t matter – as long as we’re delivering products that matter.

http://lizkeogh.com/2011/06/27/atdd-vs-bdd-and-a-potted-history-of-some-related-stuff/