Status Updates From Extreme Programming Explain...

The question is not whether or not to design, the question is WHEN to design. Incremental design suggests that the most effective time to design is in light of experience.

If it's hard to write a test, it's a signal you have a design problem not a testing problem.

Team programming is a divide, conquer and integrate problem. The integration step is unpredictable - the longer you wait,the more unpredictable and costly it becomes. Synchronous integration (with partner) better than asynchronous (when build breaks). Has built in reflection time and less context shifting.

Automatically build the whole system and run all the tests in 10 minutes

Pairing gives programmers a chance to use specialist skills, whoever holds the task)

Start the week writing automated tests that will run when the stories are completed. Then spend the rest of the week completing the stories and getting tests to pass.

When you're done exploring, bring the resultant idea, not the code, back to the team

Responsibility cannot be assigned; it can only be accepted

In software development, Perfect is a verb not an adjective

If you want people to take your advice, you need to solve more problems than you create.

Mutual Benefit - benefit me now, me later, and my customer. A win-win-win.

XP 5 values: communication, simplicity, feedback, courage, respect - to encourage team work pg 17

XP Principles: Humanity, Economics, Mutual Benefit, Self-Similarity, Improvement, Diversity, Reflection, Flow, Opportunity, Redundancy, Failure, Baby Steps, Quality, Accepted Responsibility

What actually matters is not how any given person behaves as much as how the individuals behave as part of a team and as part of an organisation.

No book of gardening, however complete, makes you a gardener. First you have to garden, then join the community of gardeners, then teach others to garden. Then you are a gardener.