JCN12 Behavior-Driven Development
•
0 likes•445 views
The document introduces Behavior Driven Development (BDD) and describes how the author implemented BDD practices at their company to help a development team meet an aggressive production goal of completing 550 story points by the end of the year. Key aspects of the introduction included establishing acceptance criteria and executable specifications for features, conducting regular release planning and backlog grooming sessions, and emphasizing exploratory testing over ad-hoc testing. Feedback loops and close collaboration between development and business partners were crucial to successfully adopting the new approach.
![The Goal of ET
1. Gain Understanding
2. Force to exhibit it’s
capabilities
3. Find Bugs
ref [5]](https://image.slidesharecdn.com/introducingbdd-121031074521-phpapp01/85/JCN12-Behavior-Driven-Development-35-320.jpg)
JCN12 Behavior-Driven Development
- 1. INTRODUCING BDD with a happy end. © Aki Salmi, 2012 cc by-sa
- 2. Who am I
- 3. Who am I (cont)
- 4. Who am I (cont.) blipper into agile since late 2006 studying to be supervisor aki.salmi@iki.fi @aksalmi
- 6. Introducing BDD Does it mean: BDD Basics OR How I introduced BDD to my current company?
- 7. History 2008 Acceptance testing with Robot Framework 2009 Acceptance testing with Cucumber 2010 first trials of using cucumber to collaborate with the customers. You can buy the book from http://pragprog.com/book/hwcuc/the-cucumber-book
- 8. 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?”
- 9. I DID WHAT I WAS BEST AT...
- 10. NOTHING
- 11. NOTHING to hinder development זּĴǰ
- 12. Where to lead? formation matters
- 13. Personal Touch live your dream transparency empathy, care optimism
- 14. Minor changes informative workspace (big kanban wall) new acceptance testing tool easy way to introduce new process closer cooperation with the business
- 15. The magic date 1.7.2011 “This needs to be done - We require You to complete 550 SP by end of this year”
- 16. Calculus 15SP / 2wk / team 2 teams Estimated total velocity 60SP / month Work enough until mid- April 2012.
- 18. “YOU NEED TO MAKE IT HAPPEN!” the business promised to help
- 19. The End?
- 20. Now it’s your call! BDD Basics Introducing change!
- 21. Walk side-by-side be always present, but not always visible
- 22. Feedback loops or how we learned about it
- 23. Ideas Features Code Matt Wynne on Refuctoring Your Cukes http://skillsmatter.com/podcast/agile-testing/refuctoring-your-cukes
- 24. The process or how we experimented it.
- 25. Release BL grooming Acceptance Criteria Executable UAT Specification defer design demo & review decisions implementation Note: this did or did not work in our context!
- 26. Release backlog grooming always off-site
- 27. ٲٱ BL AC ES WIP UAT Done here ChangeSet #
- 28. Remember: BDD is not about tools!
- 29. Communicate plans and how we are progressing
- 30. Challenges we are facing Yes, there are some.
- 31. Communicate plans so far away, no matter how close
- 32. Exploratory Testing A lot to learn Since for us it’s mostly…
- 33. ad-hoc testing ... aiming to catch bugs flying around?
- 34. INSTEAD OF…
- 35. The Goal of ET 1. Gain Understanding 2. Force to exhibit it’s capabilities 3. Find Bugs ref [5]
- 36. Feedback loops or how we think about it now
- 37. Business Process (UAT) Feature (ET) Story (ET) Scenario tests builds TDD pairing
- 38. What made this possible? 700 525 350 Linear extrapolation Expected progress w/ 100% linear growth 175 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
- 39. Story of ‘550’
- 40. Say what you say - 6 words.
- 41. Luck, that is your best friend!
- 42. Sit together, talk together, smile together
- 43. Build Trust! And help them experiment
- 44. Thank you! Feedback appreciated! aki.salmi@iki.fi @aksalmi