Agile2013

Traditional requirements approaches don’t work, but user stories and acceptance criteria are often not enough.

So, what is the answer?

Testable examples!

Testable examples, sometimes called executable specifications, provide a lightweight, objective description of a need. They serve as a **common language across roles**, from business to the development team, allowing us to **understand and improve our business rules**. As an added benefit they can be used to automate acceptance level testing.

In this workshop we will create several testable examples allowing you to immediately apply this technique in your work.