Hier finden Sie wissenschaftliche Publikationen aus den Fraunhofer-Instituten.

Inspections and pair programming - competing or complementary?

Experiences from an expert eWorkshop
: Carbon, R.; Ciolkowski, M.; Denger, C.; Lindvall, M.; Shull, F.; Costa, P.; Rombach, H.D.; Basili, V.R.

Fulltext urn:nbn:de:0011-n-285389 (154 KByte PDF)
MD5 Fingerprint: ac6fb51f4cc34aa638b2bb6fc83a52bd
Created on: 20.05.2005

Kaiserslautern, 2005, VII, 14 pp. : Ill., Lit.
IESE-Report, 029.05/E
Reportnr.: 029.05/E
Report, Electronic Publication
Fraunhofer IESE ()
inspection; e-workshop; experience; ViSEK; pair programming

The common goal of the two practices Pair Programming and Inspections is to produce high quality software. Even though they have a common goal, their approaches are different, and they are typically used in different situations. Pair programming is typically applied as a part of agile development methodologies, such as Extreme Programming, whereas Inspections are often applied in plan-driven or CMM-based methodologies. In order to gain a better understanding of these two practices and their strengths and weaknesses, we facilitated an expert eWorkshop. Our goals were to compare the two practices as well as to understand in which situations the two practices can be best applied. Our eWorkshop discussion highlighted several differences in the benefits that can be expected from the practices (along dimensions such as objectivity of review and achievable level of quality), indicating that the practices can be considered complementary in order to achieve the full range of effects.