Behaviour DrivenDevelopmentGetting the words right...
What?
Define the system in terms of itsbehaviour—what it should do.
Why?
Software design isnot an assembly line.
Upfront planning has diminishingreturns as the system evolves.
Everyone should refer to the samesystem using the same language.
Every change to the system shouldhave verifiable value to the business.
How?
Epic?Vision   Goal   Capability   Feature   Story   Scenario
To deliver capabilitieswe design features.
As a <Role>I want <Feature>In order to gain <Benefit>
Scenarios provide examplesof people using the system.
Given <Conditions>When I do <Action>Then I expect <Outcome>
Given <Conditions>When I do <Action>Then I expect <Outcome>
An ongoing conversation aboutwhat the product should do.
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Upcoming SlideShare
Loading in …5
×

Behaviour Driven Development

518 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
518
On SlideShare
0
From Embeds
0
Number of Embeds
25
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Behaviour Driven Development

  1. 1. Behaviour DrivenDevelopmentGetting the words right...
  2. 2. What?
  3. 3. Define the system in terms of itsbehaviour—what it should do.
  4. 4. Why?
  5. 5. Software design isnot an assembly line.
  6. 6. Upfront planning has diminishingreturns as the system evolves.
  7. 7. Everyone should refer to the samesystem using the same language.
  8. 8. Every change to the system shouldhave verifiable value to the business.
  9. 9. How?
  10. 10. Epic?Vision Goal Capability Feature Story Scenario
  11. 11. To deliver capabilitieswe design features.
  12. 12. As a <Role>I want <Feature>In order to gain <Benefit>
  13. 13. Scenarios provide examplesof people using the system.
  14. 14. Given <Conditions>When I do <Action>Then I expect <Outcome>
  15. 15. Given <Conditions>When I do <Action>Then I expect <Outcome>
  16. 16. An ongoing conversation aboutwhat the product should do.

×