ATDD Pattern Workshop Summary
As the AAFTT community continues to share ideas about tool support for Acceptance Test Driven Development (ATDD), we notice that a shift is taking place. Discussions on the yahoo group and at the 2010 workshop in Orlando branched out to also include things like: the ATDD process and workflow, adopting ATDD, and addressing our ambiguous terminology.
One way we want to explore these topics is by developing a pattern language to capture the successful ways that teams balance the forces affecting the adoption and practice of ATDD within different contexts. The initial pattern language workshops (full day October 1, 2010 in London, England, and an abbreviated intro/writers workshop demo in October 6, 2010 in Berlin Germany) will start to establish the architecture of the pattern language, and produce some initial draft patterns.
This is the first step in growing a pattern language, a process that always takes time and requires community involvement and commitment throughout. We will be holding subsequent workshops to refine the pattern language architecture, and focus on completing specific patterns within the language.
This post provides a summary of the activities and outcomes that we produced in these initial sessions. A follow up post will provide an initial glimpse as to the current vision for the next steps for collaboratively creating the ATDD community of practice pattern language.
(text in red is a place holder for missing information … participants, please contact me with updates)
(missing: links to their blog post of the event)
October 1, 2010 London, England: Gojko Adzic, Jennitta Andrea, Laurent Bossavit, Mario Cardinal, David Evans, Steve Freeman, Markus Gaertner, Elisabeth Hendrickson, Jez Humble, Liz Keogh, Antony Marcano, Chris Matts, Linda Rising (facilitator), Joseph Wilk
October 6, 2010 Berlin, Germany: Gojko Adzic, Jennitta Andrea, Lisa Crispin, David Evans, Markus Gaertner, Janet Gregory, Janne Härkönen, Elisabeth Hendrickson, Juha Rantanen, Linda Rising (facilitator)
Create an initial architecture for a pattern language to capture the successful ways that teams balance the forces affecting the adoption and practice of ATDD within different contexts, start writing some of the patterns, workshop some of the patterns, plan for the on-going work on the pattern language
(London only) Jennitta led a discussion about the scope of the ATDD pattern language, using these slides as reference.
Linda presented the following:
- Presentation slide deck for all three topics, which were video-taped in Berlin:
- intro to patterns & pattern template overview part 1,
- pattern template overview part 2,
- intro to pattern writers workshop & demo workshop <note I need help editing this in order to upload to youtube … let me know if you can help>
(London only) We spent a short time individually brainstorming patterns (one pattern per sticky note). Then we re-assembled to share our ideas and collectively group them into affinity groups by virtue of which flip chart page they were placed on, and how they were clustered with other sticky notes. This is a very early start to our pattern language architecture. The interesting thing to reflect on is the breadth of topics that were brought up by this diverse group.<links to photos>
The sticky notes & flip charts were transcribed into a spreadsheet:
- Each worksheet = one flip chart sheet
- Each row = cluster of related sticky notes
- Each cell = one sticky note (name, contributor, short summary)
(London only) We had about 45 minutes to select one of the sticky notes and write as much of the pattern as possible (given the standard pattern template that we just learned. The patterns do not have names yet – they are listed here by their initial aliases.
- Elisabeth Hendrickson & Liz Keogh: Breaking the model. Context questioning. Should it really?
- Markus Gaertner: Essential Examples
- ???: Get it wrong
- David Evans & Gojko Adzic: Feature-set hierarchy, break down story documentation after implementation, regression suire, feature documentation
- Jez Humble: Scenario-based tests, regression suite, curated acceptance suite, the Ottomans (also attributed to David Rice, Martin Fowler, Ben Butler-Cole, Jeff Rogers)
- Mario Cardinal, Chris Matts: Illustrating with Examples, Illustrate user stories with Examples, Concrete over abstract
- Jennitta Andrea: Big picture, process tracability
<missing patterns by Laurent Bossavit, Steve Freeman, Antony Marcano, Joseph Wilk>