Extreme programming practices: Difference between revisions

Revision as of 19:51, 12 February 2025

Revision as of 05:13, 26 March 2025

Line 1:

'''[[Extreme programming]]''' ('''XP''') is an [[agile software development]] methodology used to implement [[software]] systems. This article details the practices used in this methodology. Extreme programming has 12 practices, grouped into four areas, derived from the [[best practices]] of [[software engineering]].<ref name="XPExplained">Beck, K. ''Extreme Programming Explained: Embrace Change'' 2nd. ed. Addison-Wesley, 2000 pp. 54</ref>

==Fine -scale feedback==

=== Pair programming ===

Line 8:

The pairs are not fixed; programmers switch partners frequently, so that everyone knows what everyone is doing, and everybody remains 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).

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

Line 113 ⟶ 112:

* Get a task card: The programmer gets the task card for one of the tasks to which he or she has committed.

* Find a Partnerpartner: The programmer will implement this task along with another programmer. This is further discussed in the practice of [[Pairpair Programmingprogramming]].

* Design the task: If needed, the programmers will design the functionality of the task.

* Implement the task using [[Testtest-driven development]] (TDD) (see below)

* Run Functionalfunctional test: Functional tests (based on the requirements in the associated user story and task card) are run.

=== Test driven development ===