Your SlideShare is downloading. ×
0
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Behaviour Driven Development
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Behaviour Driven Development

281

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
281
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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

×