eXtreme Programming

eXtreme Programming

1. Features

   • Reduce the cost of change
   • Requirements determined at the beginning of the development project, then fixed from that point on
   • Cost of changing the requirements at a later stage will be high

2. Communication

   • No overemphasis on documentation
   • Talk between developers and users is key

3. Simplicity

   • Start with the simplest solution
     • Code for today
     • Don't plan for weeks or months ahead
       • User requirements may change
       • Users may not need what is planned for the future

4. Feedback

   • System Feedback
     • Unit Tests
     • Integration Tests
   • Customer Feedback
     • Acceptance tests are written by the customers and the testers
     • They get concrete feedback about the current state of their system
       • Review is planned once every two or three weeks to allow the customer to easily steer the development
   • Team Feedback
     • Customers come up with new requirements in the planning
       • Team directly gives an estimation of the time (and cost) that it will take to implement

5. Courage

   • Have the courage to:
     • Code for today
     • Not worry about future planning
     • Be amenable to change (constantly)
     • Throw away source code
     • Be persistent

6. Respect

   • Respect given and gained from the other members of the team
   • Trust your peers