Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

An ATDD Case Study

2,909 views

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
  • Be the first to comment

  • Be the first to like this

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

×