Abstract
There is a great deal of skepticism surrounding whether or not the Extreme Programming (XP) methodology has the potential to work for large-scale projects. This paper highlights two software development projects that used XP. The projects were similar but the implementation, decision-making and functional requirements varied considerably. This paper documents the advantages and disadvantages of XP experienced in these projects, highlights how the process regarding team growth evolved and matured, and discusses the lessons learned.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Beck, K., Fowler, M.: Planning Extreme Programming, p. 118 (2000)
Beck, K.: Extreme Programming Explained:Embrace Change, pp. 21–90 (2000)
Bond, M.: SamsTeach Yourself J2EE in 21 Days, p. 16 (2002)
Broemmer, D.: J2EE Best Practices, p. 11 (2003)
Crocker, R.: The 5 Reasons XP Can’t Scale and What to do About Them. In: XP Conference, Villasimius, Italy, May 20–23 (2001)
Fowler, M., et al.: Refactoring Improving the Design of Existing Code (xvi, 58)
Grand, M.: Patterns in Java: Vol. 2(1) (1999)
Meade, E.: Website: http://www.objectmentor.com
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2003 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Fredrick, C. (2003). Extreme Programming: Growing a Team Horizontally. In: Maurer, F., Wells, D. (eds) Extreme Programming and Agile Methods - XP/Agile Universe 2003. XP/Agile Universe 2003. Lecture Notes in Computer Science, vol 2753. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-45122-8_2
Download citation
DOI: https://doi.org/10.1007/978-3-540-45122-8_2
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-40662-4
Online ISBN: 978-3-540-45122-8
eBook Packages: Springer Book Archive