Announcing the AAFTT Pattern Language Workshop on October 1, 2010 in London England:
As the AAFTT community continues to share ideas about tool support for 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 workshop (October 1, 2010 in London, England) 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.
(*ATDD (acceptance test driven development) is the placeholder term we will continue to use until the community has come up with a standardized name).
We are now accepting registrations at http://aaftt-2010patternworkshop.crowdvine.com. As with our previous workshops, the cost for attending is 0. You will, however, have to pay your own travel costs.
Registration space is very limited, and the event is fast approaching, so it is important for you to answer all of the profile questions as fully as possible. The ideal candidate has prior experience with ATDD on real projects, has a strong background in patterns, and has the energy to continue to contribute beyond this initial workshop.
Registration does not guarentee a spot in the workshop. You will receive an email to confirm acceptance in the workshop.
To reach their full potential, checked examples must be rendered in a form that speaks to the business sponsors. The agile loop will not be closed until the sponsor's new goals and desires are influenced by, and cast in terms of, the current examples. The phrases, "domain language" and "living document", alludes to this influence. However, all AAFTT workflows should call out this loop as a primary and indispensable flow.