JetScootr's Journal: Thuds

Here's the deal: I love to program, been doing it professionally for many years. I'm up to learn some new stuff: artificial intelligence (ai), specifically, artificial life, genetic programming, etc. I also want to learn extreme programming, and maybe convince my coworkers/company, etc to implement at least some of the practices. I know, as a solo programmer, I can't do most XP stuff; but I will try to do what I can. I'm going to post excerpts of my project notebook here, then ask other developers if this matches their experiences in implementing XP at their workplace.
This is done on my employer's computers, but on my own time, after hours so I don't interfere with any other users by loading down the system. The system is an SGI 12000, 8 cpus, running IRIX 6.5. I'm writing this in C. Yes, my employer's policies do allow me to do this. I won't post the code I produce, not cuz it's that special, but because I don't know how the copyright thing works out. I know the code should be mine, but being on the company's computers could result in misunderstandings, so it won't get posted. Sorry.
'Thuds' is the name of the project, and the alife I'll be creating. They'll have a 2.1d world to roam around in, based on a rectangular coordinate grid. Each spot on grid can hold zero or one thud, a variety of zero or more types of plants; a spot will have 'texture', in that ease of travel over the spots will vary, based on 'dirt','water','hill','rock',etc.
Thuds will be able to sense their surroundings and will have a fitness function that determines life, health, death, etc periodically. Thuds senses will be localized and will not be task specific.
Thuds will have a list of functions they can perform. In the first major version, thuds will not be able learn, but the goal is to produce a version where the thuds do learn. Thuds will have dna that describes their initial conditions and potentials, and they will reproduce sexually, with some mutation.
Project Plan:
XP methods will be used, such as one person can do alone. The Values that I will try to apply are communication (with myself, forward and backward in time), Simplicity, Feedback, Courage. Principals: Traceability, Education, Demonstration, Elegance. Practices: RCS will store code versions, Unit tests will be coded first, automated, and will all pass before each iteration is complete.
The code will be kept neat; I will also document all aspects of this project as I develop it. Energy - I will work on code only when my mind is properly attentive and I can focus and enjoy the work. Iterations will be fairly short by XP standards - I'm going for one per programming session. A session for me will be 1-4 hours in length.
For each iteration, I will document: The story, design, unit test plan, review of performance, list of code, tests and data produced.