Extreme Programming

*Welcome!*
Call for help today 507-261-1050

12 Commandments of Extreme Programming
Credited by David Petranek of Progress Software to Wired Magazine (Sept. 2003)
which quotes a book called Extreme Programming Explained (copyright 2000) by K. Beck.

1 - The Planning Game => Meet with coders, managers and customer each week to schedule tasks for next phase. Update plan regularly.

2 - Small Releases => Put a simple system into production quickly, then release new versions on a short cycle.

3 - Metaphor => Create an analogy expressing workings of new system.

4 - Simple Design => Design simply, and remove complexity at every stage.

5 - Testing => Write test programs that assure every portion of code runs flawlessly before attempting new task.

6 - Refactoring => Edit code to simplify, add flexibility, or remove redundancy.

7 - Pair Programming => Write all code with two programmers at one machine.

8 - Collective Ownership => Permit any team member to change code anywhere at anytime.

9 - Continuous Integration => Bring components of program together several times per day to ensure they work in concert.

10 - 40-Hour Week => Strive to work no more than 40 hours. Never work overtime in a second week in a row

11 - Onsite Customer => Include a real, live user on team, available full-time to answer questions.

12 - Coding Standards => Agree-upon styles and nomenclature to promote easy understanding of code function.