An ATDD Case Study
So what’s the problem?
Acceptance CriteriaGiven I am a logged in userWhen I go to the final checkout pageThen I should see the total cost of the ...
The 3 Amigos
The 3 Amigos     “…it’s like delivering a baby.”
Feature: Process an orderGiven I am a logged in userWhen I go to the final checkout pageThen I should see the total cost o...
Definition of Done
The Board
“Before                     ”What happens when testing isn’t included in yourdefinition of done
“After                      ”What happens when testing IS included in yourdefinition of done
Who Writes the Tests
Co-location
“The Pod”
Open workspace
Continuous Integration
Reasonably Thorough            Requirements"Walking on water and developing software from aspecification are easy if both ...
Project Management•   Self-directed teams•   Everyone is responsible•   PMs lay out the roadmap•   Shared risk with the bu...
An Incremental Process
Why work incrementally towards  continuous improvement?
We’re not there yet…• Continuous improvement across teams• Better involvement with business sponsors• More visibility of c...
Thanks!• Paul Bahler  – pbahler@igsenergy.com  – @PaulBahler• Kevin Chivington  – kchivington@igsenergy.com• Jon Kruger  –...
An ATDD Case Study
An ATDD Case Study
Upcoming SlideShare
Loading in...5
×

An ATDD Case Study

1,810

Published on

Presented at the Columbus ATDD Developers Group in April 2011 with Paul Bahler (@paulbahler) and Kevin Chivington from IGS Energy.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,810
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Need to break down features enough so that you can discuss them at a granular levelRegardless of estimation method, this is a good time to right-size stories (estimating, re-estimating, or breaking down the story further)
  • Need to break down features enough so that you can discuss them at a granular levelRegardless of estimation method, this is a good time to right-size stories (estimating, re-estimating, or breaking down the story further)
  • An “on-going conversation” throughout the life of the user story / card.If BA finds something, developer and tester are informed.If Dev finds something, BA and QA are informed.If QA finds something, BA and Dev are informed.“Close the loop” and keep all domains aware of any changes / gaps / problems / decisions.
  • “Insanity: doing the same thing over and over again and expecting different results.” ~Albert Einstein
  • Transcript of "An ATDD Case Study"

    1. 1. An ATDD Case Study
    2. 2. So what’s the problem?
    3. 3. Acceptance CriteriaGiven I am a logged in userWhen I go to the final checkout pageThen I should see the total cost of the orderbroken down by product cost, tax, and shippingcharges And I should see the total cost of the order
    4. 4. The 3 Amigos
    5. 5. The 3 Amigos “…it’s like delivering a baby.”
    6. 6. Feature: Process an orderGiven I am a logged in userWhen I go to the final checkout pageThen I should see the total cost of the order broken down by productcost, tax, and shipping chargesAnd I should see the total cost of the order• Order total = total cost of products on the order + tax + shipping charges• Tax: – Ohio = 7% – Michigan = 6.5% – Other states = 0%• Shipping: – If total cost of products (before tax >= $25), shipping is free, otherwise $5
    7. 7. Definition of Done
    8. 8. The Board
    9. 9. “Before ”What happens when testing isn’t included in yourdefinition of done
    10. 10. “After ”What happens when testing IS included in yourdefinition of done
    11. 11. Who Writes the Tests
    12. 12. Co-location
    13. 13. “The Pod”
    14. 14. Open workspace
    15. 15. Continuous Integration
    16. 16. Reasonably Thorough Requirements"Walking on water and developing software from aspecification are easy if both are frozen." ~ Edward V.Berard
    17. 17. Project Management• Self-directed teams• Everyone is responsible• PMs lay out the roadmap• Shared risk with the business• Risk based testing
    18. 18. An Incremental Process
    19. 19. Why work incrementally towards continuous improvement?
    20. 20. We’re not there yet…• Continuous improvement across teams• Better involvement with business sponsors• More visibility of continuous integration build• 75% of test cases automated in 2012
    21. 21. Thanks!• Paul Bahler – pbahler@igsenergy.com – @PaulBahler• Kevin Chivington – kchivington@igsenergy.com• Jon Kruger – jon@jonkruger.com – @JonKruger
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×