Agile software development methods: Review and analysis

VTT Publications

Volumn , Issue 478, 2002, Pages 3-107

  Abrahamsson, Pekka ^a   Salo, Outi ^a   Ronkainen, Jussi ^a   Warsta, Juhani ^b  

^a VTT TECHNICAL RESEARCH CENTRE OF FINLAND   (Finland)

^b UNIVERSITY OF OULU   (Finland)

Author keywords

Agile methods; Agile modelling; Agile processes; Extreme programming; Open source software development; Software development; Software project management

Indexed keywords

EID: 0036431046     PISSN: 12350621     EISSN: 14550849     Source Type: Book Series    
DOI: None     Document Type: Review

References (88)

1. Abrahamsson, P. (2002). Commitment nets in software process improvement. Annals of Software Engineering, 13: 407-438.
2. Agarwal, R. and Prasad, J. (2000). A field study of the adoption of software process innovations by information systems professionals. IEEE Transactions on Engineering Management 47(3): 295-308.
3. Alexander, C. (1979). The Timeless Way of Building. New York, Oxford University Press.
4. Ambler, S. (2002a). Agile Modeling: Effective Practices for Extreme Programming and the Unified Process. New York, John Wiley & Sons, Inc.
5. Ambler, S. (2002b). Lessons in Agility from Internet-Based Development. IEEE Software, 19(2): 66-73.
6. Ambler, S. W. (2002c). Duking it out. Software Development 10, July.
7. Anderson, A., Beattie, R., Beck, K., Bryant, D., DeArment, M., Fowler, M., Fronczak, M., Garzaniti, R., Gore, D., Hacker, B., Handrickson, C., Jeffries, R., Joppie, D., Kim, D., Kowalsky, P., Mueller, D., Murasky, T., Nutter, R., Pantea, A. and Thomas, D. (1998). Chrysler Goes to "Extremes". Case Study. Distributed Computing (October): 24-28.
8. Baskerville, R. (1998). Designing information systems security. Chichester, UK, John Wiley.
9. Baskerville, R., Travis, J. and Truex, D. P. (1992). Systems without method: The impact of new technologies on information systems development projects. In: Kendall, K. E., Lyytinen, K. and DeGross, J. I. (eds.). Transactions on the impact of computer supported technologies in information systems development. Amsterdam, Elsevier Science Publications: 241-260.
10. Bayer, S. and Highsmith, J. (1994). RADical software development. American Programmer 7(6): 35-42.
11. Beck, K. (1999a). Embracing Change With Extreme Programming. IEEE Computer 32(10): 70-77.
12. Beck, K. (1999b). Extreme programming explained: Embrace change. Reading, Mass., Addison-Wesley.
13. Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., Kern, J., Marick, B., Martin, R., Mellor, S., Schwaber, K., Sutherland, J. and Thomas, D. (2001). Manifesto for Agile Software Development. (22.3.2002) http://AgileManifesto.org.
14. Bergquist, M. and Ljungberg, J. (2001). The power of gifts: organizing social relationships in open source communities. Information Systems Journal 11(4): 305-320.
15. Boehm, B. (2002). Get Ready For The Agile Methods, With Care. Computer 35(1): 64-69.
16. Coad, P., LeFebvre, E. and De Luca, J. (2000). Java Modeling In Color With UML: Enterprise Components and Process. Prentice Hall.
17. Cockburn, A. (1998). Surviving Object-Oriented Projects: A Manager's Guide. Addison Wesley Longman.
18. Cockburn, A. (2000). Writing Effective Use Cases. The Crystal Collection for Software Professionals. Addison-Wesley Professional.
19. Cockburn, A. (2002a). Agile Software Development. Boston, Addison-Wesley.
20. Cockburn, A. (2002b). Agile Software Development Joins the "Would-Be" Crowd. Cutter IT Journal 15(1): 6-12.
21. Coplien, J. O. (1998). A Generative Development Process Pattern Language. In: Rising, L. (ed.). The Patterns Handbook. New York, Cambridge University Press: 243-300.
22. Coyne, R. (1995). Designing Information Technology in the Postmodern Age. Cambridge, Mass., MIT Press.
23. Crowston, K. and Scozzi, B. (2002). Open source software projects as virtual organisations: competency rallying for software development. IEE Proceedings - Software 149(1): 3-17. (Pubitemid 34474679)
24. Cunningham, W. (1996). Episodes: A Pattern Language of Competitive Development. In: Vlissides, J. (ed.). Pattern Languages of Program Design 2. New York, Addison-Wesley.
25. DeMarco, T. and Lister, T. (1999). Peopleware. New York, Dorset House.
26. Dempsey, B., Weiss, D., Jones, P. and Greenberg, J. (2002). Who Is and Open Source Software Developer. CACM 45(2): 67-72.
27. Dhillon, G. (1997). Managing information systems security. London, UK, MacMillan Press.
28. Dobrica, L. and Niemelä, E. (2002). A survey on software architecture analysis methods. IEEE Transactions on Software Engineering 28(7): 638-653.
29. DSDM Consortium (1997). Dynamic Systems Development Method, version 3. Ashford, Eng., DSDM Consortium.
30. eWorkshop (2002). Summary of the second eworkshop on agile methods. (8.8.2002) http://fc-md.umd.edu/projects/Agile/SecondeWorkshop/ summary2ndeWorksh.htm.
31. Favaro, J. (2002). Managing Requirements for Business Value. IEEE Software, 19: 15-17.
32. Feller, J. and Fitzgerald, B. (2000). A Framework Analysis of the Open Source Software Development Paradigm. 21st Annual International Conference on Information Systems, Brisbane, Australia.
33. Gallivan, M. (2001). Striking a balance between trust and control in a virtual organization: a content analysis of open source software case studies. Information Systems Journal 11(4): 273-276.
34. Ghosh, R. and Prakash, V. (2000). The Orbiten Free Software Survey. (3.5.2002) orbiten.org/ofss/01.html.
35. Gilb, T. (1988). Principles of Software Engineering Management. Wokingham, UK, Addison-Wesley.
36. Glass, R. L. (1999). The realities of software technology payoffs. Communications of the ACM 42(2): 74-79.
37. Glass, R. L. (2001). Agile Versus Traditional: Make Love, Not War! Cutter IT Journal 14(12): 12-18.
38. Grenning, J. (2001). Launching XP at a Process-Intensive Company. IEEE Software 18: 3-9.
39. Haungs, J. (2001). Pair programming on the C3 project. Computer 34(2): 118-119.
40. Hawrysh, S. and Ruprecht, J. (2000). Light Methodologies: It's Like Déjà Vu All Over Again. Cutter IT Journal. 13: 4-12.
41. Highsmith, J. (2002). Agile software development ecosystems. Boston, MA., Pearson Education.
42. Highsmith, J. and Cockburn, A. (2001). Agile Software Development: The Business of Innovation. Computer 34(9): 120-122. (Pubitemid 32839711)
43. Highsmith, J. A. (2000). Adaptive Software Development: A Collaborative Approach to Managing Complex Systems. New York, NY, Dorset House Publishing.
44. Hightower, R. and Lesiecki, N. (2002). Java Tools for Extreme Programming. New York, Wiley Computer Publishing.
45. Humphrey, W. S. (1995). A discipline for software engineering. Addison Wesley Longman, Inc.
46. Hunt, A. and Thomas, D. (2000). The Pragmatic Programmer. Addison Wesley.
47. Jacobsen, I. (1994). Object-Oriented Software Engineering. New York, Addison-Wesley.
48. Jacobsen, I., Christerson, M., Jonsson, P. and Overgaard, G. (1994). Object-Oriented Software Engineering: A Use-Case-Driven Approach. Reading, MA, Addison-Wesley.
49. Jeffries, R., Anderson, A. and Hendrickson, C. (2001). Extreme Programming Installed. Upper Saddle River, NJ, Addison-Wesley.
50. Kruchten, P. (1996). A Rational Development Process. Crosstalk 9(7): 11-16.
51. Kruchten, P. (2000). The Rational Unified Process: an Introduction. Addison-Wesley.
52. Krueger, C. (2002). Eliminating the adoption barrier. IEEE Software 19(4): 29-31.
53. Lakoff, G. and Johnson, M. (1998). Philosophy in the Flesh. New York, Basic Books.
54. Lerner, J. and Tirole, J. (2001). The Simple Economics of Open Source. (20.05.2002) http://www.people.hbs.edu/jlerner/publications.html.
55. Martin, R. C. (1998). The Process. Object Oriented Analysis and Design with Applications. Addison Wesley: 93-108.
56. Maurer, F. and Martel, S. (2002a). Extreme programming: Rapid development for Web-based applications. IEEE Internet Computing 6(1): 86-90. (Pubitemid 34198233)
57. Maurer, F. and Martel, S. (2002b). On the Productivity of Agile Software Practices: An Industrial Case Study. (page accessed August 16, 2002) http://sern.ucalgary.ca/∼milos/papers/2002/MaurerMartel2002c.pdf.
58. McCauley, R. (2001). Agile Development Methods Poised to Upset Status Quo. SIGCSE Bulletin 33(4): 14-15.
59. Miller, D. and Lee, J. (2001). The people make the process: commitment to employees, decision making, and performance. Journal of Management 27: 163-189. (Pubitemid 33622881)
60. Miller, G. G. (2001). The Characteristics of Agile Software Processes. The 39th International Conference of Object-Oriented Languages and Systems (TOOLS 39), Santa Barbara, CA.
61. Mockus, A., Fielding, R. and Herbsleb, J. (2000). A Case Study of Open Source Software Development: The Apache Server. 22nd International Conference on Software Engineering, ICSE 2000, Limerick, Ireland, 263-272.
62. Moore, G. A. (1995). Inside the tornado. New York, HarperBusiness.
63. Nandhakumar, J. and Avison, J. (1999). The fiction of methodological development: a field study of information systems development. Information Technology & People 12(2): 176-191.
64. Naur, P. (1993). Understanding Turing's universal machine: Personal style in program description. The Computer Journal 36(4): 351-372.
65. O'Reilly, T. (1999). Lessons from Open Source Software Development. Communications of the ACM Vol. 42(No. 4): 32-37.
66. Palmer, S. R. and Felsing, J. M. (2002). A Practical Guide to Feature-Driven Development. Upper Saddle River, NJ, Prentice-Hall.
67. Parnas, D. L. and Clements, P. C. (1986). A rational design process: How and why to fake it. IEEE Transactions on Software Engineering 12(2): 251-257.
68. Pfeffer, J. (1998). The human equation : building profits by putting people first. Boston, MA, Harvard Business School Press.
69. Pöyhönen, J. (2000). Uusi varallisuusoikeus. (In Finnish). Helsinki, Lakimiesliiton Kustannus.
70. Rising, L. and Janoff, N. S. (2000). The Scrum software development process for small teams. IEEE Software 17(4): 26-32.
71. Schuh, P. (2001). Recovery, Redemption, and Extreme Programming. IEEE Software 18(6): 34-41.
72. Schwaber, K. (1995). Scrum Development Process. OOPSLA'95 Workshop on Business Object Design and Implementation. Springer-Verlag.
73. Schwaber, K. and Beedle, M. (2002). Agile Software Development With Scrum. Upper Saddle River, NJ, Prentice-Hall.
74. Sharma, S., Sugumaran, V. and Rajagopalan, B. (2002). A framework for creating hybrid-open source software communities. Information Systems Journal 12(1): 7-25. (Pubitemid 36721331)
75. Smith, J. (2001). A Comparison of RUP and XP. Rational Software White Paper. http://www.rational.com/media/whitepapers/TP167.pdf.
76. Sol, H. G. (1983). A feature analysis of information systems design methodologies: Methodological considerations. In: Olle, T. W., Sol, H. G. and Tully, C. J. (eds.). Information systems design methodologies: A feature analysis. Amsterdam, Elsevier: 1-8.
77. Sommerville, I. (1996). Software engineering. New York, Addison-Wesley.
78. Song, X. and Osterweil, L. J. (1991). Comparing design methodologies through process modeling. 1st International Conference on Software Process, Los Alamitos, Calif., IEEE CS Press.
79. Song, X. and Osterweil, L. J. (1992). Toward objective, systematic design-method comparisons. IEEE Software 9(3): 43-53.
80. Stapleton, J. (1997). Dynamic systems development method - The method in practice. Addison Wesley.
81. Succi, G. and Marchesi, M. (2000). Extreme Programming Examined: Selected Papers from the XP 2000 Conference. XP 2000 Conference, Cagliari, Italy, Addison-Wesley.
82. Sultan, F. and Chan, L. (2000). The adoption of new technology: The case of object-oriented computing in software companies. IEEE Transactions on Engineering Management 47(1): 106-126. (Pubitemid 30553433)
83. Takeuchi, H. and Nonaka, I. (1986). The New Product Development Game. Harvard Business Review Jan./Feb.: 137-146.
84. Truex, D. P., Baskerville, R. and Travis, J. (2000). Amethodical systems development: The deferred meaning of systems development methods. Accounting, Management and Information Technology 10: 53-79.
85. Wall, D. (2001). Using Open Source for a Profitable Startup. Computer December: 158-160.
86. Warsta, J. (2001). Contracting in Software Business: Analysis of evolving contract processes and relationships. Department of Information Processing Science. Oulu, University of Oulu, Finland: 262.
87. Wiegers, K. E. (1998). Read my lips: No new models. IEEE Software 15(5): 10-13.
88. Williams, L., Kessler, R. R., Cunningham, W. and Jeffries, R. (2000). Strengthening the Case for Pair Programming. IEEE Software 17(4): 19-25.