Details
| Originalsprache | Englisch |
|---|---|
| Titel des Sammelwerks | Agile Processes in Software Engineering and Extreme Programming |
| Untertitel | 11th International Conference, XP 2010, Proceedings |
| Seiten | 117-131 |
| Seitenumfang | 15 |
| ISBN (elektronisch) | 978-3-642-13054-0 |
| Publikationsstatus | Veröffentlicht - 2010 |
| Veranstaltung | 11th International Conference on Agile Processes in Software Engineering and Extreme Programming, XP 2010 - Trondheim, Norwegen Dauer: 1 Juni 2010 → 4 Juni 2010 |
Publikationsreihe
| Name | Lecture Notes in Business Information Processing |
|---|---|
| Band | 48 LNBIP |
| ISSN (Print) | 1865-1348 |
Abstract
Pair Programming has often been reported to be beneficial in software projects. To better understand where these benefits come from we evaluate the aspect of intra-pair communication. Under the assumption that the benefits stem from the information being exchanged, it is important to analyze the types of information being communicated. Based on the Goal Question Metric method we derive a set of relevant metrics and apply them in an eXtreme Programming class room project. Data covering a total of 22.9 hours of intra-pair communication was collected. We found that only 7% of the conversations were off-topic (e.g. private), 11% about requirements, 14% about design, and 68% about implementation details (e.g. syntax). Accordingly, a great share of the information being exchanged in Pair Programming is on a low level of abstraction. These results represent a first data point on what kind of information is communicated to what extent during Pair Programming.
ASJC Scopus Sachgebiete
- Betriebswirtschaft, Management und Rechnungswesen (insg.)
- Management-Informationssysteme
- Ingenieurwesen (insg.)
- Steuerungs- und Systemtechnik
- Betriebswirtschaft, Management und Rechnungswesen (insg.)
- Betriebswirtschaft und Internationales Management
- Informatik (insg.)
- Information systems
- Mathematik (insg.)
- Modellierung und Simulation
- Entscheidungswissenschaften (insg.)
- Informationssysteme und -management
Zitieren
- Standard
- Harvard
- Apa
- Vancouver
- BibTex
- RIS
Agile Processes in Software Engineering and Extreme Programming: 11th International Conference, XP 2010, Proceedings. 2010. S. 117-131 (Lecture Notes in Business Information Processing; Band 48 LNBIP).
Publikation: Beitrag in Buch/Bericht/Sammelwerk/Konferenzband › Aufsatz in Konferenzband › Forschung › Peer-Review
}
TY - GEN
T1 - Towards understanding communication structure in Pair Programming
AU - Stapel, Kai
AU - Knauss, Eric
AU - Schneider, Kurt
AU - Becker, Matthias
PY - 2010
Y1 - 2010
N2 - Pair Programming has often been reported to be beneficial in software projects. To better understand where these benefits come from we evaluate the aspect of intra-pair communication. Under the assumption that the benefits stem from the information being exchanged, it is important to analyze the types of information being communicated. Based on the Goal Question Metric method we derive a set of relevant metrics and apply them in an eXtreme Programming class room project. Data covering a total of 22.9 hours of intra-pair communication was collected. We found that only 7% of the conversations were off-topic (e.g. private), 11% about requirements, 14% about design, and 68% about implementation details (e.g. syntax). Accordingly, a great share of the information being exchanged in Pair Programming is on a low level of abstraction. These results represent a first data point on what kind of information is communicated to what extent during Pair Programming.
AB - Pair Programming has often been reported to be beneficial in software projects. To better understand where these benefits come from we evaluate the aspect of intra-pair communication. Under the assumption that the benefits stem from the information being exchanged, it is important to analyze the types of information being communicated. Based on the Goal Question Metric method we derive a set of relevant metrics and apply them in an eXtreme Programming class room project. Data covering a total of 22.9 hours of intra-pair communication was collected. We found that only 7% of the conversations were off-topic (e.g. private), 11% about requirements, 14% about design, and 68% about implementation details (e.g. syntax). Accordingly, a great share of the information being exchanged in Pair Programming is on a low level of abstraction. These results represent a first data point on what kind of information is communicated to what extent during Pair Programming.
KW - Communication
KW - Empirical study
KW - Pair Programming
UR - http://www.scopus.com/inward/record.url?scp=84862104325&partnerID=8YFLogxK
U2 - 10.1007/978-3-642-13054-0_9
DO - 10.1007/978-3-642-13054-0_9
M3 - Conference contribution
AN - SCOPUS:84862104325
SN - 978-3-642-13053-3
T3 - Lecture Notes in Business Information Processing
SP - 117
EP - 131
BT - Agile Processes in Software Engineering and Extreme Programming
T2 - 11th International Conference on Agile Processes in Software Engineering and Extreme Programming, XP 2010
Y2 - 1 June 2010 through 4 June 2010
ER -