Circle of Life, Spiral of Death: Are XP Teams Following the Essential Practices?
- 2.2k Downloads
Many of the twelve carefully defined practices of Extreme Programming are tightly coupled. The various practices have checks and balances on each other and are, in many ways, dependant on each other. Therefore, neglecting essential practices can have sub-optimal or negative consequences to team results. The practices that are actually utilized in team development can often be attributed to the perceptions of the value and difficulty of the practices by the developers on the team. Through two surveys answered by 27 developers, we have assessed the utilization of and the sentiments towards the XP practices. In general, these developers we surveyed valued and utilized most of the practices.
KeywordsSurvey Participant Small Release Project Velocity Pair Programming Collective Ownership
Unable to display preview. Download preview PDF.
- 1.Beck, K., Extreme Programming Explained:Embrace Change. 2000: Addison-Wesly.Google Scholar
- 2.Jeffries, R., Circle of life, Spiral of Death. Extreme Programming Perspectives ed, ed. G.S. M. Marchesi, D. Wells, L. Williams. 2002, Boston, MA: Addison-Wesly, in press.Google Scholar
- 3.Gittins, R., Extreme Programming-Questionnaire, School of Informatics University of Wales Bangor.Google Scholar
- 4.Laurie A. Williams, R.R.K., All I Really Need to Know about Pair Programming I Learned In Kindergarten, in Communications of the ACM. May 2000.Google Scholar
- 5.Williams, L.A., The Collaborative Software Process PhD Dissertation. 2000, University of Utah: Salt Lake City, UT.Google Scholar
- 6.Williams, L. A., Pair Programming Illuminated. 2002, Boston, MA: Addison Wesly.Google Scholar
- 7.Auer, K. and R. Miller, Extreme Programming Applied. 2002, Boston, MA: Addison Wesly.Google Scholar
- 8.Fowler, M., Refactoring: Improving the Design of Existing Code. August, 1999, MA: Addison Wesly.Google Scholar