1. Behaviour Driven
Development
Getting the words right...

2. What?

3. Define the system in terms of its
behaviour—what it should do.

5. Why?

6. Software design is
not an assembly line.

8. Upfront planning has diminishing
returns as the system evolves.

10. Everyone should refer to the same
system using the same language.

12. Every change to the system should
have verifiable value to the business.

14. How?

15. Epic?
Vision Goal Capability Feature Story Scenario

16. To deliver capabilities
we design features.

17. As a <Role>
I want <Feature>
In order to gain <Benefit>

18. Scenarios provide examples
of people using the system.

19. Given <Conditions>
When I do <Action>
Then I expect <Outcome>

20. Given <Conditions>
When I do <Action>
Then I expect <Outcome>

21. An ongoing conversation about
what the product should do.