Extreme programming practices: Difference between revisions

Revision as of 06:01, 28 January 2013

Revision as of 14:40, 8 April 2013

Line 2:

==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 after minute to hour periods.

Line 32 ⟶ 33:

==== Release planning ====

===== Exploration phase =====

Line 83 ⟶ 85:

==== Iteration planning ====

===== Exploration phase =====

Line 120 ⟶ 123:

==Continuous process==

=== Continuous integration ===

The development team should always be working on the latest version of the software. Since different team members may have versions saved locally with various changes and improvements, they should try to upload their current version to the code repository every few hours, or when a significant break presents itself. Continuous integration will avoid delays later on in the project cycle, caused by integration problems.

Line 130 ⟶ 134:

==Shared understanding==

=== Coding standard ===

Coding standard is an agreed upon set of rules that the entire development team agree to adhere to throughout the project. The standard specifies a consistent style and format for source code, within the chosen programming language, as well as various programming constructs and patterns that should be avoided in order to reduce the probability of defects.<ref>{{cite book | last = Kolawa | first = Adam | coauthors = Huizinga, Dorota | title = Automated Defect Prevention: Best Practices in Software Management | url = http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470042125.html | year = 2007 | publisher = Wiley-IEEE Computer Society Press | ___location =| page=75| pages =426 | isbn = 0-470-04212-5 }}</ref> The coding standard may be a standard conventions specified by the language vendor (e.g. The Code Conventions for the Java Programming Language, recommended by Sun), or custom defined by the development team.

=== Collective code ownership ===

Line 145 ⟶ 150:

==Programmer welfare==

=== Sustainable pace ===

The concept is that programmers or software developers should not work more than 40 hour weeks, and if there is overtime one week, that the next week should not include more overtime. Since the development cycles are short cycles of continuous integration, and full development (release) cycles are more frequent, the projects in XP do not follow the typical crunch time that other projects require (requiring overtime).