12

From ggc

analysis design implemetation testing deployment- a large part of deployment programs are support REALISTIC PLANNING- CUSTOMERS ARE TO MAKE BUSINESS DECISIONS, PROGRAMMERS ARE TO MAKE TECHNICAL DECISIONS. UPDATE THE PLAN WHEN IT CONFLICTS WITH REALITY.

small releases- release a useful system quickly, then release updeates on a very short cycle.

metaphor-all programmewrs should have a simple shared story that explains the system under develpoment

simplicity-design everything to be as simple as possible instead of prepairing for future complexity

testing-both programmers and cutomers are to write test cases. the system is continuously tested.

refractoring-programmers are to restructure the system continuously to improve the code and eliminate duplication

pair programming- put programmers togeather in pairs, and require each to write code on a single computer

collective owenership- all programmers have permission to change all codeas it becomes neccessary

continuous integration-whenever a task is completed, build the entire system and test it

40 hour a week- dont cover up unrealistic schedule with bursts of heroic effort.

on site customer-an actual customer of the system is to be accessible to team memebers at all times

codeing standards-programmers are to follow standards that emphasize self documenting code.