Copyright © Fraunhofer IESE 2004 First International Workshop on Software Quality (SOQUA 2004) Erfurt, Germany, September 30, 2004 IESE —OverviewOverview —IntroductionIntroduction —ProcessProcess —OutlookOutlook —DiscussionDiscussion Outline Slide 3 The 12 XP practices The Planning Game — quickly determine scope of next release Small releases — put a simple system in production quickly then release new version on a short cycle Metaphor — guide development with a simple shared story Simple design — system should be as simple as possible, complexity should be removed if at all possible Testing — continually write unit tests, customers write functional tests Refactoring — restructure the system without changing behavior Pair programming — all code written with 2 programmer at 1 machine Collective ownership — anyone can change code anywhere anytime Continuous integration — integrate and build many times a day 40-hour week — work no more than 40h/wk as a rule On-site customer — include a real, live user on the team full time Coding standards — code in accord.
{}