Abstract
We conducted an experiment attempting to compare XP with a traditional approach to student software engineering projects. We tasked two groups of student teams with producing a simple room reservation system, one group following a traditional development process, the other using XP. We observed little actual difference between the products delivered by either process. However, in our opinion this is due to certain deficiencies in the way XP was realized in this instance, rather than fundamental flaws in the process itself.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Boehm, B.W.: Anchoring the software process. IEEE Software 13 (1996) 73–82
Farell, C., Narang, R., Kapitan, S., Webber, H.: Towards an effective onsite customer practice. [4] 52–55
Lappo, P.: No pain, no XP — Observations on teaching and mentoring extreme programming to university students. [4] 35–38
Succi, G., Marchesi, M., eds. In Succi, G., Marchesi, M., eds.: Proceedings of the Third International Conference on Extreme Programming and Agile Processes in Software Engineering, Alghero, Sardinia, Italy (2002)
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
Noll, J., Atkinson, D.C. (2003). Comparing Extreme Programming to Traditional Development for Student Projects: A Case Study. In: Marchesi, M., Succi, G. (eds) Extreme Programming and Agile Processes in Software Engineering. XP 2003. Lecture Notes in Computer Science, vol 2675. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-44870-5_56
Download citation
DOI: https://doi.org/10.1007/3-540-44870-5_56
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-40215-2
Online ISBN: 978-3-540-44870-9
eBook Packages: Springer Book Archive