JCN12 Behavior-Driven Development

587 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
587
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

JCN12 Behavior-Driven Development

  1. 1. INTRODUCING BDD with a happy end.© Aki Salmi, 2012 cc by-sa
  2. 2. Who am I
  3. 3. Who am I (cont)
  4. 4. Who am I (cont.)blipperinto agile since late 2006studying to be supervisoraki.salmi@iki.fi @aksalmi
  5. 5. Introducing BDDDoes it mean: BDD BasicsOR How I introduced BDD to my current company?
  6. 6. History2008 Acceptancetesting with RobotFramework2009 Acceptancetesting with Cucumber2010 first trials of usingcucumber to collaboratewith the customers. You can buy the book from http://pragprog.com/book/hwcuc/the-cucumber-book
  7. 7. Early spring 2011 @ Lindorff I started as Scrum Master for a team of 9. Weekly sprints. Mostly failing to deliver Agile coaches visiting us. Discussions. Every. Single. Morning. “What’s wrong with this all?”
  8. 8. I DID WHAT I WAS BEST AT...
  9. 9. NOTHING
  10. 10. NOTHINGto hinder development effort
  11. 11. Where to lead? formation matters
  12. 12. Personal Touchlive your dreamtransparencyempathy, careoptimism
  13. 13. Minor changesinformative workspace (big kanban wall)new acceptance testing tool easy way to introduce new processcloser cooperation with the business
  14. 14. The magic date 1.7.2011“This needs to be done - We require You to complete550 SP by end of this year”
  15. 15. Calculus 15SP / 2wk / team 2 teams Estimated total velocity 60SP / monthWork enough until mid- April 2012.
  16. 16. which resulted in...
  17. 17. “YOU NEED TO MAKE IT HAPPEN!” the business promised to help
  18. 18. The End?
  19. 19. Now it’s your call!BDD Basics Introducing change!
  20. 20. Walk side-by-sidebe always present, but not always visible
  21. 21. Feedback loops or how we learned about it
  22. 22. Ideas Features CodeMatt Wynne on Refuctoring Your Cukes http://skillsmatter.com/podcast/agile-testing/refuctoring-your-cukes
  23. 23. The processor how we experimented it.
  24. 24. Release BL
grooming Acceptance
 Criteria Executable
 UAT Specification defer designdemo & review decisions implementation Note: this did or did not work in our context!
  25. 25. Release backlog grooming always off-site
  26. 26. Dates
 BL AC ES WIP UAT Donehere ChangeSet #
  27. 27. Remember: BDD is not about tools!
  28. 28. Communicate plans and how we are progressing
  29. 29. Challenges we are facingYes, there are some.
  30. 30. Communicate plans so far away, no matter how close
  31. 31. Exploratory TestingA lot to learnSince for us it’s mostly…
  32. 32. ad-hoc testing... aiming to catch bugs flying around?
  33. 33. INSTEAD OF…
  34. 34. The Goal of ET1. Gain Understanding2. Force to exhibit it’s capabilities3. Find Bugs ref [5]
  35. 35. Feedback loopsor how we think about it now
  36. 36. Business Process (UAT) Feature (ET) Story (ET) Scenario tests builds TDD pairing
  37. 37. What made this possible?700525350 Linear extrapolation Expected progress w/ 100% linear growth175 Expected progress w/ aggressive growth Done + Approved 0 22.6 6.7 20.7 3.8 17.8 31.8 14.9 28.9 12.10 26.10 9.11 23.11 7.12 21.12 4.1. 18.1 1.2 15.2 29.2
  38. 38. Story of ‘550’
  39. 39. Say what you say - 6 words.
  40. 40. Luck,that is your best friend!
  41. 41. Sit together, talk together,smile together
  42. 42. Build Trust!And help them experiment
  43. 43. Thank you!Feedback appreciated!aki.salmi@iki.fi @aksalmi

×