a few additions to Caristi's slides:

*   YAGNI - You Aren't Going to Need It

*   CRC cards are involved in design sessions
    *   Class, Responsibilities, and Collaboration Cards
    
*   Spike solution
    *   purpose is to reduce risk

    *   A spike solution is a very simple program to explore
        potential solutions

*   User stories
    *   written by the customer
    *   in the format of about 3 sentences of text in the customer's
        terminology without techno-syntax

*   Stand-up meeting
    *   why standing? to keep it short...!

The 12-practices (plus...)
1*   The planning game
2*   Simple design
3*   pair programming
4*   the 40-hour week
5*   small releases
6*   unit testing
7*   acceptance testing
8*   collective ownership of the code
9*   on-site customer
10*   metaphor
11*   refactoring
12*   continuous integration
13*   coding standards

14*   CRC cards
15*   spike solutions
16*   stand-up meeting
17*   user stories