#executablespecification

[gfader]

What is “Example Mapping” and why should I care?

Nice article that explains “Example Mapping” by Matt Wynne

Concrete examples are a tremendous way to help us explore the problem domain, and they make a great basis for our acceptance tests.

Layout those examples on a table with “Example Mapping”.

I like this because its visual and it follows along the 3Cs: Card, Conversation, Confirmation. Something to try in your next Backlog refinement session.

Introducing Example Mapping https://cucumber.io/blog/2015/12/08/example-mapping-introduction

Fun exercise for teaching Example Mapping https://speakerdeck.com/mattwynne/rules-vs-examples-bddx-london-2014

[gfader]

How up2date is your documentation? Not at all?

Check out  http://scenarioo.org by @zuehlke_group

"Automated documentation of applications through UI tests"

[gfader]

Do you know the difference between a desirement and a requirement? via @ElegantCoder‎

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