Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News "Agile Practice" Patterns Wiki is Up

"Agile Practice" Patterns Wiki is Up

At XP2006, Amr Elssamadisy announced a new wiki site for collecting Agile Practice Patterns. There's not much there yet - but you can already find results from ChiliPlop 2006 and XP2006 on the site. And really, it's only been up a few days, and it is a wiki so any practitioners with experience to share can collaborate there. These are the pages and patterns already in progress:

Bad Requirements
ChiliPlop 2006 Results
Cross Testing
Developers/Managers Misalignment
Fear of Losing Control
Fearless Change
Frequent Release
Learn Then Share
Lots of Bugs Found by Customer
Onsite Customer
Onsite Customer
Scared To Share
Static Information Radiator
Test Driven Development
Unpaid Debt
XP2006 Patterns

There appear to be a number of pattern forms in use on the site... perhaps the simplest pattern being Ward Cunningham's Therefore-But form, the one most used on the original C2 wiki.


Patterns are a way to capture knowledge and abstract it, distill it down to an essential and clear form that can help someone else address a similar problem.  Patterns are not simply ideas written in a certain form - pattern mining is a whole process unto itself: pattern writers at AG Communication Systems use pattern mining to get ideas for patterns, which they then improve using a writers' workshop.

Patterns moved from the domain of architecture into the mainstream of object-oriented software design with the advent of the original book Design Patterns: Elements of Reusable Object Oriented Software.  This is not surprising, as architect Christopher Alexander's Notes on the Synthesis of Form was required reading for researchers in computer science throughout the 1960's. Since that first book, many more have used this device to address software design issues - its popularity suggests it is a useful way to think and communicate.

Subsequently, patterns have been used in other areas of the software world too:  Organizational Patterns of Agile Software Development by Coplien and Harris looks at the people side of software development, Fearless Change: Patterns for Introducing New Ideas by Rising and Manns addresses the human challenges of organizational change (not just in IT), and Software for Your Head: Core Protocols for Creating and Maintaining Shared Vision by McCarthy and McCarthy provides patterns specifically for collaborative teamwork.

FYI: if you find this topic interesting, you might want to know that the patterns folks hang out here. Well, when they are online :-)

Rate this Article