One XP experience: introducing agile (XP) software development into a culture that is willing but not ready

ABSTRACT

The main question to be asked is "Does Extreme Programming (XP) make sense as a development methodology in a diverse, multidisciplinary web development environment? This environment includes diverse, and perhaps, distributed teams requiring close coordination with multidisciplinary skills -- information architecture, visual design, XML, Java and others. The potential is to make the development process more responsive to users' needs and changing business requirements. This could have high impact on outcomes of the development process, decreasing cost, decreasing time to deployment, and increasing user satisfaction. The challenges are to adapt and reconcile the corporate and the agile culture processes and methodologies without seriously compromising either. We will discuss our experience from conception into implementation of XP through the first release that incorporates several iteration cycles. We will discuss the positive and negative forces and how they have or have not been resolved to date.

REFERENCES

• 1: Kent Beck, Extreme programming explained: embrace change, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 2: Kent Beck , Martin Fowler, Planning Extreme Programming, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2000
• 3: {3} J. Bergin, HtmlFixture, http://fitnesse.org/FitNesse.HtmlFixture, accessed June 2004.
• 4: {4} J. Bergin, F. Grossman, Extreme Construction, http://csis.pace.edu/~bergin/extremeconstruction/, accessed June 2004.
• 5: {5} CMMI Product Team, Capability Maturity Model Integration (CMMI) Version 1.1: CMMI for Software Engineering (Continuous Representation) , Technical Report CMU/SEI-2002-TR028 & ESC-TR-2002-028, August 2002.
• 6: Norman L. Kerth, Project retrospectives: a handbook for team reviews, Dorset House Publishing Co., Inc., New York, NY, 2001
• 7: {7} M. Kircher, P. Jain, A. Corsaro, D. Levine, Distributed eXtreme Programming, http://www.agilealliance.org/articles/articles/Distr ibutedXP.pdf, accessed June 2004.
• 8: {8} P. Merel, Extreme Hour, http://c2.com/cgi/wiki?ExtremeHour, http://home.san/rr.com/merel/xhour.ppt, accessed June 2004.
• 9: {9} M. Paulk, B. Curtis, M. B. Chrssis, C. V. Weber, Capability Maturity Model for Software Version 1.1, Technical Report CMU/SEI-93-TR- 024 & ESC-TR-93-177, February 1993.
• 10: Hugh Robinson , Helen Sharp, XP Culture: Why the twelve practices both are and are not the most significant thing, Proceedings of the Conference on Agile Development, p.12, June 25-28, 2003
• 11: Michael K. Spayd, Evolving Agile in the Enterprise: Implementing XP on a Grand Scale, Proceedings of the Conference on Agile Development, p.60, June 25-28, 2003
• 12: Doug Wallace , Isobel Raggett , Joel Aufgang, Extreme Programming for Web Projects, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2002
• 13: {13} N. Wallace, P. Baily, N. Ashworth, Managing XP with Multiple or Remote Customers, http://www.agilealliance.org/articles/articles/Wall ace-Bailey-- ManagingXPwithMultipleorRemoteCustomers.pdf, accessed June 2004.

INDEX TERMS

Primary Classification:
  D. Software
  D.1 PROGRAMMING TECHNIQUES
      D.1.3 Concurrent Programming
          Subjects: Distributed programming

Additional Classification:
  I. Computing Methodologies
  I.7 DOCUMENT AND TEXT PROCESSING
      I.7.2 Document Preparation

          Nouns: XML

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development

General Terms:
Human Factors, Management