Patterns for groups Transitioning To Extreme Programming. You've bought into the concept of Extreme Programming. You know what all the main practices are (if not, go to Extreme Programming Core Practices), but you're having trouble getting your organization to adopt certain of the practices, or you're just not sure where to start in the first place. This page is for you.
This page lists patterns and Proto Patterns for Adopting Xp. It does not list patterns for adopting practices that are Almost Extreme Programming, although these may or may not be worthwhile practices (e.g. Customer Shadowing).
Click the title for pages in the Adopting Xp Pattern Language.
Patterns
Note: Items marked below with an asterisk (*) are Proto Patterns (currently most are, but hopefully this will improve soon). Promote a Proto Pattern to a Pattern when it has been shown to have been Used Three Times.
How do we ...
Begin (and where)?
Adopt acceptance testing?
Adopt simple design?
Adopt Sustainable Pace (Forty Hour Week)?
Or, how to go about Extreme Programming In Enemy Territory.
From the Xp Mailing List poll "What are the top 3 practices you find difficult to put in practice at your work place? (Please, check only 3. Thanks!)":
On-Site Customer 56 20.44% ******************** Pair Programming 45 16.42% **************** Planning Game 32 11.68% ************ Metaphor 31 11.31% *********** Testing 23 8.39% ******** 40-Hour Week 18 6.57% ******* Collective Ownership 17 6.20% ****** Continuous Integration 15 5.47% ***** Simple Design 15 5.47% ***** Refactoring 12 4.38% **** Coding Standards 5 1.82% ** Small Releases 5 1.82% **
(There's some discussion at groups.yahoo.com . Does anyone have a reference for the original discussion when the poll was announced. It's _hard_ searching 70,000 messages!)
See original on c2.com