Home | deutsch  | Legals | Data Protection | Sitemap | KIT

Are Reviews an Alternative to Pair Programming?

Are Reviews an Alternative to Pair Programming?
Name:

Zeitschriftenartikel

Year:

2004 

Author:

Matthias Müller
Links:PDF

Zusammenfassung

From the first presentation of extreme programming on, pair programming has attracted a wide range of programmers to work together in front of one display. The proposed advantages of pair programming are a faster development cycle and code with higher quality. However, the nearly doubled personal cost when compared to single developers seems to outweigh these advantages. Instead of showing the superiority of pair programming, we seek for an alternative. Can a single developer be assisted by an already known technique with which he produces 80 percent of the quality of pairs with only 20 percent of the cost? The answer with some restrictions is: yes, he can. Reviews are a reasonable candidate with respect to code quality and cost.

Beteiligte Mitarbeiter (zufällige Reihenfolge)
Titel Vorname Nachname

Projekte
Titel


Bibtex

@article{,
author={Matthias M{\"u}ller},
title={Are Reviews an Alternative to Pair Programming?},
year=2004,
month=Dec,
publisher={Kluwer},
volume={9},
url={https://ps.ipd.kit.edu/downloads/za_2004_reviews_alternative_pair_programming.pdf},
abstract={From the first presentation of extreme programming on, pair programming has attracted a wide range of programmers to work together in front of one display. The proposed advantages of pair programming are a faster development cycle and code with higher quality. However, the nearly doubled personal cost when compared to single developers seems to outweigh these advantages. Instead of showing the superiority of pair programming, we seek for an alternative. Can a single developer be assisted by an already known technique with which he produces 80 percent of the quality of pairs with only 20 percent of the cost? The answer with some restrictions is: yes, he can. Reviews are a reasonable candidate with respect to code quality and cost.},
number={4},
journal={Empirical Software Engineering},