DenkzeitWiki

Extreme Programming

If it's not tested, it's broken.[1]

Einführung

Extreme Programming is a discipline of software development based on values of simplicity, communication, feedback, and courage. It works by bringing the whole team together in the presence of simple practices, with enough feedback to enable the team to see where they are and to tune the practices to their unique situation. [2]

• http://www.rolemodelsoftware.com/moreAboutUs/publications/xpDistilled.php
• http://www.softwarereality.com/ExtremeProgramming.jsp
  
  
• Wiki:ExtremeProgramming
  • Wiki:ExtremeProgrammingSummary
  • Wiki:ExtremeProgrammingRoadmap
  • Wiki:ExtremeProgrammingCorePractices
    
  
  
• http://www.xprogramming.com/
  
  
• http://www.jera.com/techinfo/xpfaq.html
  
• Wiki:CrcCard --CRC-Karten
  • Wiki:CrcCardsAreCognitive
  
  
• Wiki:UserStory --User Story

design first, write tests to that design, then program, test, perform refactoring and iterate

• Wiki:XpSimplicityRules

Always implement things when you actually need them, never when you just foresee that you need them.

Just do it in tiny increments.

Do the simplest thing that could possibly work.

• Wiki:WhatIsSimplest
• Occam's Razor@Wikipedia

The simplest explanation is the best. When multiple explanations are available for a phenomenon, the simplest version is preferred.

Regeln XP Rules

• Coding
• Testing
• Listening (Planning) -> What's the problem?
• Designing -> ReFactoring

• http://martinfowler.com/articles/designDead.html --Is Design Dead? article by Martin Fowler
  
• http://patricklogan.blogspot.com/2005/02/courage-and-trust-in-software.html --Entwickler und Interessenvertreter müssen sich gegenseitig vertrauen.
  Manchmal ist ReFactoring notwenig. ReFactoring fügt aber keine neue Funktionalität hinzu. Es kann schwierig sein, das zu rechtfertigen. -> Vertrauen.

Pair Programming

• http://softwarenerd.blogspot.com/2005/03/pair-programming.html
  • via http://weblogs.goshaky.com/weblogs/page/lars/20050412#pair_programming

The differences between XP and trial-and-error are basically two-fold: first, you solve each error as it comes up, so that it doesn't compound with later errors. And second, you meant to do it that way in the first place, rather than being forced to come back and deal with unforeseen complications.

"Extreme" means these practices get "turned up" to a much higher "volume" than on traditional projects. XP ignores any other practice (like Wiki:BigDesignUpFront) that does not appear on the list. The result is stable, productive, and very rapid because the practices support each other the more they are used together without interference. An Extreme project is typically so stable and sedate it can lead to Wiki:FortyHourWeeks without any schedule slips.

Bücher

• Extreme Programming . Das Manifest von Kent Beck
• Extreme Programming, Sonderausgabe von Kent Beck
• Software entwickeln mit eXtreme Programming von Martin Lippert, Stefan Roock, Henning Wolf