At XP2005 conference in Sheffield, I attended Kent Beck's tutorial "The XP Geography: Mapping Your Next Step, a Guide to Planning Your Journey". In this session we used mind maps to explore XPv2 practices. The session was fun and it was interesting trying to write mind maps in small groups. The espoused advantages is that as mind maps are visual representations, they engage different areas of the brain and as a result help you connect ideas in a new way. Over the years, I have encountered several mind map enthusiasts but never really seriously tried using the technique. Following the workshop, I am experimenting with using mind maps in my own work. So today, I have been using mind mapping to develop some training material for Agile Summer School and I do think it helped me to clarify some of my ideas. One tip that Kent gave us is use big paper for more ideas, we used flip chart paper in the workshop with coloured felt tip pens. Another tip, that resonated with advice from Jerry Weinberg (given in his Writer's Workshop, Albuquerque), is when you get stuck just start another draft. Getting the map right first time is not important. Also to draw the mind map from your own view point, this can help work out next steps to take when moving towards a practice. Aside from mind-mapping Kent shared some other thoughts about XPv2 that I will summarize here. XP is a distillation of learning; a bunch of ideas that have proven helpful. Rather than telling someone "what to do", Kent now prefers to tell them "what I do" because the former undermines the person you are talking to. XP should not be thought of as a process like a computer program that you execute. In XP there's no one starting point, it depends upon your context. The XP practices help you work out things you can do to improve your software. Kent now recognizes that the key to implementing change are Accountability (which he talked about in his keynote "Another Notch") and Community. Making a change is like moving a point in a spider's web, it sets up a tension for for it to move back to the original state. Community can hold you through the emotional discomfort of the change until you start to reap the benefits. It was surprising to hear that Kent is "severely embarrassed by the first edition" of XP because it promotes a programmer-centric approach that suggests everyone else should change. Indeed, Kent is actually looking forward to the first edition going out of print because the message is so out of tune with his current thinking. This is somewhat sad as I think many XP practitioners have a soft spot for the first edition of "XP Explained" which was a call to arms to start writing code with "knobs turned up to 10".