09-29-2014 by Sebastian Schürmann
Some weeks ago, I startet out to write a series of blog-posts on XP practices in the format of “N tips for your XP practice” and I want to give a little more insight whats behind the idea.
Believe it or not, but not every aspect of Extreme Programming has received so much attention that there is a big load of information out there on every little practice. I realized this when I did the research for the last workshop on XP Practices. There is the C2 Wiki and others, but still some of the practices are just a name with little or none information.
It seems like a golden rule that rarely is broken: One good idea receives 10 “counter-posts” with a negative conotation, telling you why X or Y is bad. Examples?
I consider this a malpractice and I do not want to contribute to that with my company or the blogging here. So I started this series of blogposts to shed a more constructive light on things than just spreading bad karma of NEIN, NEIN, NEIN!.
When doing more research on the practices I found out that even the very complete book of James Shore, that lists a lot of the practices, is not complete enough for me. There would be a ton of things that I could share add from first-hand practical experience that I accumulated over the last years. I will ask my network of experienced practitioners for input and then share a post. The nice thing on the Number of N tips is that these can be extended when I get input in the comments.
Once a week I will use my own list of practices found in Extreme Programming and randomly select one with the following one-liner.
files=(/my/dir/*)
printf "%s\n" "${files[RANDOM % ${#files[@]}]}"This gives me the opportunity to re-visit these topics and put some work in it. The contents are needed for the training/workshop on Extreme Programming. So why not share them?
The next practice is Code and Tests (Code and Test Data in one repository). A rather technical one ;)
What practices do you want to read about? Which are the ones that keep you puzzled?