Extreme Programming (XP) is becoming popular as a software development method and there is quite a lot of literature describing its philosophy and practices. However, in all of this literature Software Configuration Management (SCM) is almost never mentioned explicitly, leaving XP practitioners with the impression that SCM is not needed and SCM people with the impression that XP is not sound from an SCM perspective. We carried out a more profound analysis of XP and its practices seen from an SCM perspective. We found that in general XP and its practices do not go against common SCM standards, if we take into consideration that the XP context is different from that of more traditional projects. However, some SCM aspects need to be made explicit and a number of SCM-specific sub-practices need to be added to make XP a complete and sound development method seen from an SCM perspective. We report on how we implemented “our findings” on several dozen XP projects and our experience from doing this through several iterations. (Less)
[1]
Kent L. Beck,et al.
Extreme programming explained - embrace change
,
1990
.
[2]
Görel Hedin,et al.
Introducing software engineering by means of extreme programming
,
2003,
25th International Conference on Software Engineering, 2003. Proceedings..
[3]
Wayne A. Babich,et al.
Software Configuration Management: Coordination for Team Productivity
,
1986
.
[4]
Ulf Asklund,et al.
Configuration Management for Open Source Software
,
2001
.
[5]
Kent L. Beck,et al.
Embracing Change with Extreme Programming
,
1999,
Computer.
[6]
Tim Mikkelsen,et al.
Practical Software Configuration Management: The Latenight Developer's Handbook
,
1997
.