UseXpAsAnAdaptiveProcess

As the paper Rules of XP http://www.rolemodelsoft.com/publications/papers/rulesOfXp.htm points out, XP is defined both by its values and its practices. And hey, even KentBeck says that you can be doing all the practices and still not be extreme.

So, if we can embrace change at the programming level, why not go one step further and integrate change into our whole programming process?

With this line of thought DoingXpByTheBook is just a starting point, and we allow our needs (on this team / on this project / in this organisation / at this point in time) to direct our particular use of XP. This way our XP adapts to both changes in the outside world (changes in the team / project etc) and to changes in what we have learnt about the outside world (knowledge about this team / project etc). --TimBacon