Extreme programming and agile methods
Subtitle: XP/Agile Universe 2003 : third XP Agile Universe Conference, New Orleans, LA, USA, August 10-13, 2003 : proceedings
By: Frank Maurer, Don Wells (eds.).
Contributors: Maurer, F.; Wells, Don, 1955-
Series: Lecture notes in computer science -- 2753.
Publisher: Springer
Published: 2003
Place of publication: Berlin; New York
Language: eng
Number of pages: 213
Subjects: Agile software development -- Congresses; eXtreme programming -- Congresses
Genres: Congresses.
Description: XPAgileUniverse2003isthethirdconferenceinaseriesrunninginNorthA- rica and attracting participants from all over the world who are interested in the research, development and application of agile software processes. Agile app- aches value people and interaction over processes and tools – moving software engineering from the process-oriented software development approaches of the 1990s towards people-oriented approaches that we are starting to see more and more in this decade. Agile approaches stress a holistic view of software deve- pers as being involved in analysis, design, implementation and testing activities, while more traditional, tayloristic approaches separate these tasks and assign them to di?erent “resources. ” Tayloristic approaches create knowledge-sharing problems as information gathered by one person needs to be handed over – usually in the form of documentation – to the next person in the chain. Agile approaches reduce the number of hand-o?s and, thus, decrease the amount of required documentation for knowledge sharing. While deemed a novelty only a few years ago, agile methods are now be- ming established in the software industry and are being applied in more and more application domains. While agile approaches move into the mainstream of software organizations, we are only now beginning to understand their bene?ts, areas of applicability, and also their dangers. This year’s conference will increase this understanding and provide a better base for industry practitioners as they assess the e?ectiveness of agile methods in their environment.