Extreme programming practices: Difference between revisions

Revision as of 14:14, 19 July 2012

Revision as of 12:54, 6 September 2012

Line 3:

==Fine scale feedback==

=== Pair programming ===

[[Pair programming]] means that all code is produced by two people programming on one task on one workstation. One programmer has control over the workstation and is thinking mostly about the coding in detail. The other programmer is more focused on the big picture, and is continually reviewing the code that is being produced by the first programmer. Programmers trade roles regularlyafter minute to hour periods.

The pairs are not fixed: it's recommended that; programmers try to mix as muchswitch aspartners possiblefrequently, so that everyone knows what everyone is doing, and everybody can becomeremains familiar with the whole system, even the parts outside their skill set. This way, pair programming also can enhance team-wide communication. (This also goes hand-in-hand with the concept of Collective Ownership).

The pairs are not fixed: it's recommended that programmers try to mix as much as possible, so that everyone knows what everyone is doing, and everybody can become familiar with the whole system. This way, pair programming also can enhance team-wide communication. (This also goes hand-in-hand with the concept of Collective Ownership).

=== Planning game ===<!-- This section is linked from [[Extreme programming]] -->

The main planning process within extreme programming is called the Planning Game. The game is a meeting that occurs once per iteration, typically once a week. The planning process is divided into two parts: