When I am introducing XP to a new team I usually start with a short overview starting with values. Of the values - Courage, Communication, Feedback and Simplicity - Courage seems to stick out like a sore thumb.
What has Courage got to do with writing code? Well, do you ever catch yourself saying - we should really get rid of this or there's a cleaner solution but we didn't get time to implement it (perhaps even EJB's are overkill here). The XP value of courage is all about following your own advice - swallowing the bitter pill - if the code could be cleaned up then get down to it and refactor.
The XP team values developers who step forward and do what needs to be done rather than living with clumsy solutions.
I looked back at c2 and found it refreshing how open the discussion on naming this value was. This set me wondering why Kent did not use the wiki for XP Explained 2nd edition...
New yahoo group http://groups.yahoo.com/group/xpbookdiscussiongroup/ for discussion of new practices (too late for review).
Recent Comments