Is extreme programming just old wine in new bottles: A comparison of two cases

Journal of Database Management

Volumn 16, Issue 4, 2005, Pages 41-61

  Hilkka, Merisalo Rantanen ^a   Tuure, Tuunanen ^b   Matti, Rossi ^a,c  

^a HELSINKI SCHOOL OF ECONOMICS   (Finland)

^b UNIVERSITY OF AUCKLAND   (New Zealand)

^c Department of Information Systems ^*

Author keywords

Agile methods; Case study; Extreme programming; Information systems development

Indexed keywords

INFORMATION ANALYSIS; PRODUCTIVITY; RESEARCH AND DEVELOPMENT MANAGEMENT; SOFTWARE ENGINEERING;

AGILE METHOD; CASE STUDY; EXTREME PROGRAMMING; INFORMATION SYSTEMS DEVELOPMENT;

COMPUTER PROGRAMMING;

EID: 27144553160     PISSN: 10638016     EISSN: 10638016     Source Type: Journal    
DOI: 10.4018/jdm.2005100103     Document Type: Article

References (62)

1. Abrahamsson, P. (2003). Extreme programming: First results from a controlled case study. In Proceedings of the Euromicro 2003, Antalya, Turkey, September 3-5.
2. Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2002). Agile software development methods: Review and analysis (no. 478). Espoo, Finland: Technical Research Centre of Finland, VTT Publications.
3. Abrahamsson, P., Warsta, J., Siponen, M. T., & Ronkainen, J. (2003). New directions on agile methods: A comparative analysis. Proceedings of the 25th International Conference on Software Engineering, Portland, OR, May 3-10.
4. Agile Manifesto. (2003). Retrieved on April 24, 2003, from http://www.agilealliance.org/
5. Andersen, N. E. et al. (1990). Professional systems development: Experience, ideas and action. Hemel Hampstead: Prentice Hall.
6. Aoyama, M. (1998). Agile software process and its experience. In. Proceedings of the International Conference on Software Engineering ICSE 1998, Kyoto, Japan, April 19-25.
7. Back, R. J., Milovanov, L., Pores, I., & Preoteasa, V. (2002). XP as a framework for practical software engineering experiments. In Proceedings of the Third International Conference on eXtreme Programming and Agile Processes in Software Engineering, Alghero, Sardinia, Italy, May 26-29.
8. Baskerville, R., Ramesh, B., Levine, L., Pries-Heje, J., & Slaughter, S. (2003). Is Internet-speed software development different? IEEE Software, 20(6), 70-77.
9. Beck, K. (1999). Extreme programming explained: Embrace change. Reading, MA: Addison-Wesley.
10. Bjerkenes, G., & Bratteteig, T. (1995). User participation and democracy: A discussion of Scandinavian research on system development. Scandinavian Journal of Information Systems, 7(1), 73-98.
11. Boehm, B. (1988). A spiral model of software development and enhancement. IEEE Computer, 27(5), 61-72.
12. Boehm, B. (2002). Get ready for agile methods, with care. IEEE Computer, 35(1), 64-69.
13. Boehm, B., Egyed, A., Kwan, J., Port, D., & Madachy, R. (1998). Using the winwin spiral model: A case study. IEEE Computer, 31(1), 33-44.
14. Boehm, B., & Turner, R. (2003). Balancing agility and discipline: A guide for the perplexed. Boston: Pearson Education, Inc.
15. Brooks, F. (1975). The mythical man month: Essays on software engineering. Reading, MA: Addison-Wesley.
16. Carmel, E., Whitaker, R D., & George, J. F. (1993). PD and joint application design: A transatlantic comparison. Communications of the ACM, 36(6), 40-48.
17. Clemont, A., & Besselaar, O. (1993). A retrospective look at PD projects. Communications of the ACM, 36(4), 29-39.
18. Cockburn, A. (2002). Agile software development. Boston: Addison-Wesley.
19. Conrad, B. (2003). Taking programming to the extreme edge. Retrieved on October 14, 2003, from http://archive.infoworld.com/articles/mt/xml/00/07/24/ 000724mtextreme.xml
20. Dahl, O.-J., &Nygaard, K. (1966). SIMULA: An ALGOL-based simulation language. Communications of the ACM, 9(9), 671-678.
21. Ehn, P. (1988). Work-oriented design of computer artifacts. Fallköping, Sweden: Arbetslivscentrum.
22. Elssamadisy, A., & Schalliol, G. (2002). Recognizing and responding to "bad smells" in extreme programming. In. Proceedings of the 24th International Conference on Software Engineering, Orlando, FL, May 19-25.
23. Evans, M. W. (1984). Productive software test management. New York: John Wiley & Sons.
24. Extreme Programming Organization. (2002). Retrieved on November 14, 2002, from http://www.extremeprogramming.org
25. Fairley, R. (1985). Software engineering concepts. New York: McGraw-Hill.
26. Greenbaum, J., & Kyng, M. (1991). Design at work: Cooperative design of computer systems. Hillsdale, NJ: Lawrence Erlbaum Associates.
27. Grudin, J. (1991). Interactive systems: Bridging the gaps between developers and users. IEEE Computer, 24(4), 59-69.
28. Hirschheim, R., Heinzl, K. K., & Lyytinen, K. (1995). Information systems development and data modeling. New York: Cambridge University Press.
29. Hirschheim, R., Klein, H. K., & Lyytinen, K. (2003). Information systems development and data modeling: Conceptual and philosophical foundations. Cambridge University Press.
30. Howard, D. (2003). Swimming around the waterfall: Introducing and using agile development in a data centric, traditional software engineering company. In Lecture notes in computer science: Vol. 2675. Proceedings of the Fifth International Conference on Product Focused Software Process Improvement PROFES 2004, (pp. 138-145).
31. Iivari, J. (1990a). Hierarchical spiral model for information-system and software- development. Part 1 : Theoretical background. Information and Software Technology, 32(6), 386-399.
32. Iivari, J. (1990b). Hierarchical spiral model for information-system and software- development. Part 2: Design process. Information and Software Technology, 32(1), 450-458.
33. Iivari, J., Hirschheim, R., & Klein, H. K. (1998). A paradigmatic analysis contrasting information systems development approaches and methodologies. Information Systems Research, 9(2), 164-193.
34. Joosten, S., & Purao, S. (2002). A rigorous approach for mapping workflows to object-oriented IS models. Journal of Database Management, 13(4), 1-19.
35. Kähkönen, T., & Abrahamsson, P. (2004). Achieving CMMI level 2 with enhanced extreme programming approach. In Lecture notes in computer science: Vol. 3009. Proceedings of Fifth International Conference on Product Focused Software Process Improvement PROFES 2004, (pp. 378-392).
36. Känsälä, K. (2004). Good-enough software process in Nokia. In Lecture notes in computer science: Vol. 3009. Proceedings of Fifth International Conference on Product Focused Software Process Improvement PROFES 2004, (pp. 424-430).
37. Klein, H. K., & Myers, M. D. (1999). A set of principles for conducting and evaluating interpretive field studies in information systems. MIS Quarterly, 25(1), 67-93.
38. Knuth, D. E. (1984). Literate programming. Computer Journal, 2 7(1), 97-111.
39. Liu, L., Pu, C., & Ruiz, D. D. (2004). A systematic approach to flexible specification, composition, and restructuring of workflow activities. Journal of Database Management, 75(1), 1-40.
40. Luqi, P. B., & Zyda, M. (1990). Graphical tool for computer-aided prototyping. Information and Software Technology, 36(3), 199-206.
41. McConnell, S. (1996). Rapid development: Taming wild software schedules. Redmond, WA: Microsoft Press.
42. McKeen, J. D., Guimaraes, T., & Wetherbe, J. C. (1994). The relationship between user participation and user satisfaction: An investigation of four contingency factors. MIS Quarterly, 18(4), 427-451.
43. Murru, O., Deias, R., & Mugheddu, G. (2003). Assessing XP at a European Internet company. IEEE Software, 20(3), 37-43.
44. Myers, M. D. (2003). Qualitative research in information systems. Retrieved on April 24, 2003, from http://www.qual.aucklandac.nz
45. Nawrocki, J., Jasinski, M., Walter, B., & Wojciechowski, A. (2002). Extreme programming modified: Embrace requirements engineering practices. In Proceedings of the IEEE Joint International Conference on Requirements Engineering (RE'02), Essen, Germany, September 9-13.
46. Paulk, M. (2001). Extreme programming from a CMM perspective. IEEE Software, 18(6), 19-26.
47. Paulk, M. C., Curtis, B., Chrissis, M. B., & Weber, C. V. (1993). The capability maturity model for software. IEEE Software, 10(4) 18-27.
48. Pressman, R. (2000). Software engineering: A practitioner's approach (5th ed.). McGraw-Hill.
49. Ramesh, B., & Jarke, M. (2001). Toward reference models for requirements traceability. IEEE Transactions on Software Engineering, 27(1), 58-93.
50. Reifer, D. J. (2002). How good are agile methods. IEEE Software, 19(4), 16-18.
51. Salo, O., & Abrahamsson, P. (2004). Empirical evaluation of agile software development: The controlled case study approach. In Lecture notes in computer science: Vol. 3009. Proceedings of 5th International Conference on Product Focused Software Process Improvement PROFES 2004, (pp. 408-423).
52. Shabe, G., Peck, S., & Hickey, R. (1977). Team dynamics in systems development and management. In Proceedings of the 15th Annual SIGCPR Conference, Arlington, VA, August 18-19.
53. Shoval, P., & Kabeli, J. (2001). FOOM: Functional- and object-oriented analysis & design of information systems: An integrated methodology. Journal of Database Management, 12(1) 15-25.
54. Smart, K. L., & Whiting, M. E. (2001). Designing systems that support learning and use: A customer-centered approach. Information & Management, 39(3), 177-190.
55. Sommerville, I. (2001). Software engineering (6th ed.). Addison-Wesley.
56. Turner, R. (2002). Agile development: Good process or bad attitude? In Lecture notes in computer science: Vol. 2559. Proceedings of Fourth International Conference on Product Focused Software Process Improvement PROFES 2002, (pp. 134-144).
57. Vanhanen, J., Jouni, J., & Kähkönen, T. (2003). Practical experiences of agility in the telecom industry. In Lecture notes in computer science: Vol. 2675. XP2003, (pp. 279-287).
58. Visconti, M., & Cook, C. R. (2004). An ideal process model for agile methods. In Lecture notes in computer science: Vol. 3009. Proceedings of the Fifth International Conference on Product Focused Software Process Improvement PROFES 2004, (pp. 431-441).
59. Walsham, G. (1995). Interpretive case studies in IS research: Nature and method. European Journal of Information Systems, 4(2), 74-81.
60. Williams, L., & Kessler, R. (2002). Pair programming illuminated. Boston: Addison-Wesley.
61. Wynekoop, J. L., & Russo, N. L. (1995). System development methodologies: Unanswered questions and the research-practice gap. Journal of Information Technology, 10(2), 65-73.
62. Wynn, E. (2001). Möbius transactions in the dilemma of legitimacy. In E. M. Trauth (Ed.), Qualitative research in IS: Issues and trends (pp. 20-44). Hershey, PA: Idea Group Publishing.