A practice that involves two people such that one person (the primary person or the pilot) works on the artifact while the other (the secondary person or the co-pilot) provides support in decision making and provides input and critical feedback on all aspects of the artifact as it evolves.
Published in Chapter:
Extreme Programming for Web Applications
Pankaj Kamthan (Concordia University, Canada)
Copyright: © 2009
|Pages: 6
DOI: 10.4018/978-1-60566-026-4.ch239
Abstract
The engineering environment of Web Applications is in a constant state of technological and social flux. These applications face challenges posed by new implementation languages, variations in user agents, demands for new services, and user classes from different cultural backgrounds, age groups, and capabilities. We require a methodical approach towards the development life cycle and maintenance of Web Applications that can adequately respond to this constantly changing environment. In this article, we propose the use of an agile methodology (Highsmith, 2002), namely Extreme Programming (XP) (Beck & Andres, 2005), for a systematic development of Web Applications. In general, agile methodologies have show to be cost-effective for projects with certain types of uncertainties (Liu, Kong, & Chen, 2006) and, according to surveys (Khan & Balbo, 2005), been successfully applied to Web Applications. The organization of the article is as follows. We first outline the background necessary for the discussion that pursues and state our position. This is followed by a discussion of the applicability and feasibility of XP practices as they pertain to Web Applications. Then the shortcomings of XP towards Web Applications are highlighted, and suggestions for improvement are presented. Next, challenges and directions for future research are outlined. Finally, concluding remarks are given.