Programming in the eXtreme: critical characteristics of agile implementations

• Autorzy: DeHondt II G. , Brandyberry A.
• Języki publikacji: EN

Abstrakty

EN

The prevalence of systems development project failures has been well documented. eXtreme Programming (XP) is a software development methodology that seeks to eliminate many of the shortcomings of cumbersome life cycle oriented traditional methodologies. We explore some of the basic tenets of XP and Agile methodologies and present the thoughts of two of the proponents and early participants in the "Agile revolution", Chet Hendrickson and Ron Jeffries. We analyze this interview utilizing an interpretive field study employing a hermeneutical circle technique. Our analysis suggests some of the characteristics of XP implementations are more critical than others. We propose a more concrete definition of what XP represents and suggest areas for future research.

Słowa kluczowe

EN

eXtreme Programming (XP); agile methodologie

• Wydawca: Oficyna Wydawnicza Politechniki Wrocławskiej
• Czasopismo: e-Informatica Software Engineering Journal
• Rocznik: 2007
• Tom: Vol. 1, nr 1
• Strony: 43--58
• Opis fizyczny: Bibliogr. 47 poz.

Twórcy

autor

DeHondt II G.

autor

Brandyberry A.

• Management & Information Systems Department, Kent State University

Bibliografia

• [1] S. Ambler. The Extreme Programming Software Process Explained. Computing Canada,26:24, March 2000.
• [2] V. Basili and A. Turner. Iterative Enhancement: A Practical Technique for Software Development.IEEE Transactions on Software Engineering, 1(4):390–396, December 1975.
• [3] K. Beck. Extreme Programming Explained. Addison-Wesley, Boston, 2000.
• [4] K. Beck and C. Andres. Extreme Programming Explained: Embrace Change 2nd Ed. Addison-Wesley, Boston, 2004.
• [5] B. Boehm. A Spiral Model of Software Development and Enhancement. ACM SIGSOFT Software Engineering Notes, 11(4):22–42, 1988.
• [6] F. Brooks. The Mythical Man Month: Essays on Software Engineering. Addison-Wesley,Reading, MA, 2003.
• [7] S. Cavaleri and K. Obloj. Management Systems: A Global Perspective. Wadsworth Publishing Copany, California, 1993.
• [8] A. Cockburn. Agile Software Development. Addison-Wesley, Boston, 2002.
• [9] A. Cockburn and J. Highsmith. Agile Software Development: The Business of Innovation.IEEE Computer, pages 120–122, September 2001.
• [10] B. Conrad. Taking Programming to the Extreme. Infoworld, page 24, July 2001. July 21,2000. available online at http://www.infoworld.com/articles/mt/xml/00/07/24/000724mtextreme.html.
• [11] W. Cunningham. Manifesto for Agile Software Development. [WWW document]. URL http://www.agilemanifesto.org/principles.html, n.d./2006.
• [12] J. Erickson, K. Lyytinen, and K. Siau. Agile Modeling, Agile Software Development, and Extreme Programming: The State of Research. Journal of Database Management, 16:88–100,October–December 2005.
• [13] B. Fitzgerald, N. Russo, and T. OKane. An Empirical Study of System Development Method Tailoring in Practice. Proceedings of the Eighth International Conference on Information Systems, pages 187–194, 2000.
• [14] M. Fowler. The New Methodology. [WWW document]. URL http://www.martinfowler.com/articles/newMethodology.html, December 2005.
• [15] B. George and L. Williams. A Structured Experiment of Test-Driven Development. Information and Software Technology, 46(5):337–342, April 2004.Programming in the eXtreme: Critical Characteristics of Agile Implementations 57
• [16] E. Germain and P. Robillard. Engineering-Based Processes and Agile Methodologies for Software Development: A Comparative Case Study. Journal of Systems and Software, 75:17–27, 2005.
• [17] A. Gopal, T. Mukhopadhyay, and M. Krishnan. The Role of Software Process and Communication in OffShore Software Development. Communications of the ACM, 45(4):193–200,March 2002.
• [18] J. Grenning. Launching Extreme Programming at a Process Intensive Company. IEEE Software, 18(6):27–33, November–December 2001.
• [19] B. Henderson-Sellers and M. K. Serour. Creating a Dual-Agility Method: The Value of Method Engineering. Journal of Database Management, 16(4):1–23, October–December 2005.
• [20] J. Highsmith. Agile Software Development Ecosystems. Addison-Wesley, Boston, MA, 2002.
• [21] J. Highsmith. Cutter Consortium Reports: Agile Project Management: Principles and Tools,volume 4(2). Cutter Consortium, Arlington, MA, 2003.
• [22] R. Hirschheim, H. Klein, and K. Lyytinen. Information Systems Development and Data Modeling. Cambridge University Press, New York, 1995.
• [23] R. Hirschheim, H. Klein, and K. Lyytinen. Information Systems Development and Data Modeling: Conceptual and Philosophical Foundations. Cambridge University Press, Boston, MA, 2003.
• [24] J. Hoffer, J. George, and J. Valacich. Modern Systems Analysis and Design. Addison-Wesley,Boston, MA, 1998.
• [25] S. Joosten and S. Purao. A Rigorous Approach for Mapping Workflows to Object-Oriented IS Models. Journal of Database Management, 13(4):1–19, October–December 2002.
• [26] H. Klein and M. Myers. A Set of Principles for Conducting and Evaluating Interpretive Field Studies in Information Systems. MIS Quarterly, 23(1):67–93, March 1999.
• [27] S. Kvale. Interviews: An Introduction to Qualitative Research Interviewing. Sage Publications,Thousand Oaks, 1996.
• [28] N. Levina and J. Ross. IT From the Vendors Perspective: Exploring the Value Proposition in Information Technology Outsourcing. MIS Quarterly, 27(3):331–364, September 2003.
• [29] L. Lindstrom and R. Jeffries. Extreme Programming and Agile Development Methodologies.Information Systems Management, 21(3):41–52, 2004.
• [30] P. Manhart and K. Schneider. Breaking the Ice for Agile Development of Embedded Software:An Industry Experience Report. Proceedings of the 26th International Conference on Software Engineering, pages 378–386, 2004.
• [31] N. Matloff. Globalization and the American IT Worker. Communications of the ACM,47(1):27–29, November 2004.
• [32] P. McBreen. Questioning Extreme Programming. Addison-Wesley, Thousand Oaks, 2003.
• [33] J. McKeen, T. Guimaraes, and J.Wetherbe. The Relationship Between User Participation and User Satisfaction: An Investigation of Four Contingency Factors. MIS Quarterly, 18(4):427–451, 1994. 58 Gerald DeHondt II, Alan Brandyberry
• [34] A. Mehmet, F. Harmsen, K. van Slooten, and R. Stegwee. On the Adaptation of an Agile Information Systems Development Method. Journal of Database Management, 16(4):24–40,October–December 2000.
• [35] H. Merisalo-Rantanen, T. Tuunanen, and M. Rossi. Is XP Just Old Wine in New Bottles. Journal of Database Management, 16(4):41–61, October–December 2000.
• [36] M. Mller. Preliminary Study on the Impact of a Pair Design Phase on Pair Programming and Solo Programming. Information and Software Technology, 48(5):335–344, May 2006.
• [37] S. Nerur, R. Mahapatra, and G. Mangalaraj. Challenges of Migrating to Agile Methodologies.Communications of the ACM, 48(5):73–78, May 2005.
• [38] M. Paulk. Extreme Programming from a CMM Perspective. IEEE Software, 18(6):19–26,November–December 2001.
• [39] C. Poole and J. W. Huisman. Using Extreme Programming in a Maintenance Environment.IEEE Software, 18(6):42–50, November–December 2001.
• [40] B. Rumpe and A. Schroder. Quantitative Survey on Extreme Programming Projects. Proceedings of the Third International Conference on Extreme Programming and Flexible Processes in Software Engineering (XP2002), Alghero, Italy, May 26-30, pages 95–100, 2002.
• [41] C. Sauer and C. Lau. Trying to Adopt Systems Development Methodologies: A Case Based Exploration of Business Users Interests. Information Systems Journal, 7(4):255–275, October 1997.
• [42] P. Schuh. Recovery, Redemption, and Extreme Programming. IEEE Software, 18(6):33–40,November–December 2001.
• [43] Software Engineering Institute. Capability Maturity Model for Software. [WWW document].URL http://www.sei.cmu.edu/cmm/, January 2006.
• [44] W. Strigel. Reports from the Field: Using Extreme Programming and Other Experiences. IEEE Software, 18(6):17–18, November–December 2001.
• [45] T. Chau and F. Maurer and G. Melnik. Knowledge sharing: Agile methods vs. tayloristic methods. Proceedings of the 12th IEEE International Workshop on Enabling Technologies:Infrastructure for Collaborative Enterprises (WETICE 03), pages 302–307, 2003.
• [46] C. Team. Chrysler Goes to “Extremes”. Distributed Computing, pages 24–28, October 1998.
• [47] D. Turk, R. France, and B. Rumpe. Assumptions Underlying Agile Software-Development Processes. Journal of Database Management, 16(4):62–87, October–December 2005.