Field experiences with eXtreme Programming: Developing an emergency response system

Ann L Fruhling, Gert Jan De Vreede

Research output: Contribution to journalReview article

79 Citations (Scopus)

Abstract

eXtreme Programming (XP) is a well-known agile software development method. While a number of reports have been published on explaining the XP methodology and the perceived benefits when using XP for system development in recent years, less is known about the actual operationalization of the XP principles. This paper presents an action research study reporting on the experiences of implementing the XP methodology in a development project for a Web-based, distributed information system. The goal of this research was to increase the understanding of how to effectively operationalize XP techniques so that the system being developed catered to today's fast-paced technological environment by allowing the developers to respond quickly to innovative and changing requirements. Overall, the research indicates that most of the XP principles could be effectively implemented; however, three of the principles required modification (i.e., testing, pair programming, customer collocation). Several benefits resulted from the usage of XP. The rapid prototyping enabled information technology developers and users to clarify system requirements, communicate openly, quickly build rapport, and create an interface that was easy to use and learn. Further, the research found that where the technology was new or foreign to the development team and the user, the XP process was flexible enough to support several iterations of technology and produce prototypes in a timely manner. Pair programming appeared to work effectively and offer value; however, it is not always practically feasible.

Original languageEnglish (US)
Pages (from-to)39-68
Number of pages30
JournalJournal of Management Information Systems
Volume22
Issue number4
DOIs
StatePublished - Mar 1 2006

Fingerprint

programming
experience
operationalization
methodology
software development
system development
action research
development project
new technology
information system
Rapid prototyping
customer
Computer programming
information technology
Information technology
Software engineering
Information systems
Emergency response
Extreme programming
Values

Keywords

  • Action research
  • Agile methodologies
  • EXtreme programming
  • Emergency response
  • Pair programming
  • Rapid prototyping
  • Software testing

ASJC Scopus subject areas

  • Management Information Systems
  • Computer Science Applications
  • Management Science and Operations Research
  • Information Systems and Management

Cite this

Field experiences with eXtreme Programming : Developing an emergency response system. / Fruhling, Ann L; De Vreede, Gert Jan.

In: Journal of Management Information Systems, Vol. 22, No. 4, 01.03.2006, p. 39-68.

Research output: Contribution to journalReview article

@article{5cb0a3cd533d4663babec6cc4116d126,
title = "Field experiences with eXtreme Programming: Developing an emergency response system",
abstract = "eXtreme Programming (XP) is a well-known agile software development method. While a number of reports have been published on explaining the XP methodology and the perceived benefits when using XP for system development in recent years, less is known about the actual operationalization of the XP principles. This paper presents an action research study reporting on the experiences of implementing the XP methodology in a development project for a Web-based, distributed information system. The goal of this research was to increase the understanding of how to effectively operationalize XP techniques so that the system being developed catered to today's fast-paced technological environment by allowing the developers to respond quickly to innovative and changing requirements. Overall, the research indicates that most of the XP principles could be effectively implemented; however, three of the principles required modification (i.e., testing, pair programming, customer collocation). Several benefits resulted from the usage of XP. The rapid prototyping enabled information technology developers and users to clarify system requirements, communicate openly, quickly build rapport, and create an interface that was easy to use and learn. Further, the research found that where the technology was new or foreign to the development team and the user, the XP process was flexible enough to support several iterations of technology and produce prototypes in a timely manner. Pair programming appeared to work effectively and offer value; however, it is not always practically feasible.",
keywords = "Action research, Agile methodologies, EXtreme programming, Emergency response, Pair programming, Rapid prototyping, Software testing",
author = "Fruhling, {Ann L} and {De Vreede}, {Gert Jan}",
year = "2006",
month = "3",
day = "1",
doi = "10.2753/MIS0742-1222220403",
language = "English (US)",
volume = "22",
pages = "39--68",
journal = "Journal of Management Information Systems",
issn = "0742-1222",
publisher = "M.E. Sharpe Inc.",
number = "4",

}

TY - JOUR

T1 - Field experiences with eXtreme Programming

T2 - Developing an emergency response system

AU - Fruhling, Ann L

AU - De Vreede, Gert Jan

PY - 2006/3/1

Y1 - 2006/3/1

N2 - eXtreme Programming (XP) is a well-known agile software development method. While a number of reports have been published on explaining the XP methodology and the perceived benefits when using XP for system development in recent years, less is known about the actual operationalization of the XP principles. This paper presents an action research study reporting on the experiences of implementing the XP methodology in a development project for a Web-based, distributed information system. The goal of this research was to increase the understanding of how to effectively operationalize XP techniques so that the system being developed catered to today's fast-paced technological environment by allowing the developers to respond quickly to innovative and changing requirements. Overall, the research indicates that most of the XP principles could be effectively implemented; however, three of the principles required modification (i.e., testing, pair programming, customer collocation). Several benefits resulted from the usage of XP. The rapid prototyping enabled information technology developers and users to clarify system requirements, communicate openly, quickly build rapport, and create an interface that was easy to use and learn. Further, the research found that where the technology was new or foreign to the development team and the user, the XP process was flexible enough to support several iterations of technology and produce prototypes in a timely manner. Pair programming appeared to work effectively and offer value; however, it is not always practically feasible.

AB - eXtreme Programming (XP) is a well-known agile software development method. While a number of reports have been published on explaining the XP methodology and the perceived benefits when using XP for system development in recent years, less is known about the actual operationalization of the XP principles. This paper presents an action research study reporting on the experiences of implementing the XP methodology in a development project for a Web-based, distributed information system. The goal of this research was to increase the understanding of how to effectively operationalize XP techniques so that the system being developed catered to today's fast-paced technological environment by allowing the developers to respond quickly to innovative and changing requirements. Overall, the research indicates that most of the XP principles could be effectively implemented; however, three of the principles required modification (i.e., testing, pair programming, customer collocation). Several benefits resulted from the usage of XP. The rapid prototyping enabled information technology developers and users to clarify system requirements, communicate openly, quickly build rapport, and create an interface that was easy to use and learn. Further, the research found that where the technology was new or foreign to the development team and the user, the XP process was flexible enough to support several iterations of technology and produce prototypes in a timely manner. Pair programming appeared to work effectively and offer value; however, it is not always practically feasible.

KW - Action research

KW - Agile methodologies

KW - EXtreme programming

KW - Emergency response

KW - Pair programming

KW - Rapid prototyping

KW - Software testing

UR - http://www.scopus.com/inward/record.url?scp=33748593114&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=33748593114&partnerID=8YFLogxK

U2 - 10.2753/MIS0742-1222220403

DO - 10.2753/MIS0742-1222220403

M3 - Review article

AN - SCOPUS:33748593114

VL - 22

SP - 39

EP - 68

JO - Journal of Management Information Systems

JF - Journal of Management Information Systems

SN - 0742-1222

IS - 4

ER -