A simple tool to assist in agile methodology adoption decisions

Journal of Decision Systems

Volumn 16, Issue 4, 2007, Pages 451-468

  McAvoy, John ^a   Sammon, David ^a   Owens, Ian ^b  

^a UNIVERSITY COLLEGE CORK   (Ireland)

^b CRANFIELD UNIVERSITY   (United Kingdom)

Author keywords

Adoption Assessment Matrix; Adoption Decision; Agile Methods; Decision Making

Indexed keywords

EID: 78751491097     PISSN: 12460125     EISSN: 21167052     Source Type: Journal    
DOI: 10.3166/jds.16.451-468     Document Type: Article

References (65)

1. Abrahamsson, P., Salo, O., Ronkainen, J., and Warsta, J., 2002. Agile software development methods, Review and analysis, Finland:VTT Publications.
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. Basili, V. R., Caldiera, G., and Rombach, D., 1994. “ The Goal Question Metric approach ”. In Encyclopedia of Software Engineering, Edited by:Marciniak, J., 528–532. Wiley & Sons Inc.
4. Beck, K., and Fowler, M., 2001. Planning extreme programming, NJ, USA:Addison Wesley.
5. Birmingham, D., 2002. Software development on a leash, NY, USA:Springer-Verlag.
6. Boehm, B., 2002. Get ready for Agile methods, with care. IEEE Computer, 35 (1):64–69.
7. Boehm, B., and Turner, R., 2003. “ Rebalancing your organizations agility and discipline ”. In Extreme programming and Agile methods–Xp/Agile universe, Edited by:Maurer, F., and Wells, D., 1–8. Berlin, Germany:Springer-Verlag.
8. Boehm, B., and Turner, R., 2004. Balancing agility and discipline, MA, USA:Pearson Education.
9. th IFIP World Computing Conference. pp. 1069–1076.
10. Burns, T., and Stalker, G., 1961. The Management of Innovation, London, England:Tavistock Publications.
11. Cockburn, A., and Highsmith, J., 2001. Agile software development:The people factor. IEEE Computer, 34 (11):131–133.
12. Coesmans, P., 2003. “ DSDM in a non-IT project ”. In DSDM Business focused development, Edited by:Stapleton, J., 113–119. London, UK:Pearson Education.
13. Cole, G., 1988. Management Theory and Practice, Hants, England:DP Publications.
14. De Marco, T., and Boehm, B., 2002. The Agile methods fray. IEEE Computing, 35 (6):90–92.
15. Dolan, S., Garcia, S., and Auerbach, A., 2003. Understanding and managing chaos in organisations. International Journal of Management, 20 (1):23–35.
16. DSDM. 1998. Guidelines for the introducing DSDM into an organisation. DSDM Consortium. 1998, Kent, England.
17. Fichman, R., and Kemerer, C., 1999. The illusory diffusion of innovation:An examination of assimilation gaps. Information Systems Research, 10 (3):255–275.
18. Fowler, M., and Highsmith, J., 2001. The Agile manifesto. Software Development, 9 (8):28–32.
19. Gandossy, R., 2003. The need for speed. Journal of Business Strategy, 24 (1):29–33.
20. Gallivan, M., 2001. Organizational adoption and assimilation of complex technological innovations:Development and application of a new framework. DATABASE, 32 (3):51–85.
21. Gallivan, M., 2004. Examining IT professionals’ adaptation to technological change:The influence of gender and personal attributes. DATABSE, 35 (3):28–49.
22. Glass, R., 2001. Agile versus traditional:Make love not war. Cutter IT Journal, 14 (12):12–18.
23. Green, G., Collins, R., and Hevner, A., 2004. Perceived control and diffusion of software process innovations. Journal of High Technology Management, 15 (1):123–144.
24. Greening, J., 2001. Launching extreme programming at a process-intensive company. IEEE Software, 18 (6):27–33.
25. Hayes, J., and Finnegan, P., 2003. Assessing the potential of e-business models, Towards a framework for assisting decision-makers. European Journal of Operational Research, 160 (2):365–379.
26. Highsmith, J., 2001. Opening Statement. Cutter IT Journal, 14 (12):2–4.
27. Highsmith, J., 2002. Agile Software Development Ecosystems, MA, USA:Addison Wesley.
28. Highsmith, J., 2004. Agile Project Management, MA, USA:Pearson Education.
29. Highsmith, J., and Cockburn, A., 2001. Agile software development:The business of innovation. IEEE Computer, 34 (9):120–122.
30. Jeffries, R., 2001. “ Card magic for managers:low-tech techniques for design and decisions ”. In Beyond chaos:The expert edge in managing software development, Edited by:Constantine, L., 27–32. NJ, USA:Addison-Wesley.
31. Johansen, K., and Perkins, A., 2002. “ Establishing an Agile testing team ”. In Extreme Programming and Agile methods–XP/Agile Universe Chicago, 52–59. NY, USA:Springer-Verlag.
32. st Century. American Programmer, 11 (2):24–29.
33. Kalita, T., 2003. “ DSDM in process improvement ”. In DSDM Business focused development, Edited by:Stapleton, J., 175–191. NY, USA:Pearson Education.
34. th International Conference in Extreme Programming and Agile processes in software engineering (XP 2003). 2003, Genoa, Italy. pp. 363–365.
35. Kirkpatrick, R., Walker, J., and Firth, R., 1992. “ Software development risk management:an SEI appraisal ”. In SEI Technical Review, PA, USA:Software Engineering Institute.
36. Klein, G. A., 1993. “ A recognition-primed decision (RPD) model of rapid decision making ”. In Decision Making in Action, Models and Methods, Edited by:Klein, G. A., Orasanu, J., Calderwood, R., and Zsambok, C. E., 138–147. Nordwood, NJ:Ablex.
37. Klein, G. A., 2002. “ The fiction of optimization ”. In Bounded Rationality:The Adaptive Toolbox, Edited by:Gigerenzer, G., and Selten, R., 103–121. MA:MIT Press.
38. th Extreme programming and Agile processes in software engineering Conference. 2004, Germany.
39. Koontz, H., O'Donnell, C., and Weihrich, H., 1980. Management, Tokyo, Japan:McGraw-Hill.
40. Kruchen, P., 2001. Agility with the RUP. Cutter IT Journal, 14 (12):27–33.
41. Levine, L., Baskerville, R., Link, J., Pries-Heje, J., Ramesh, B., and Slaughter, S., 2002. “ Discovery Colloquim:Quality software development at internet speed ”. In Technical Report CMU/SEI- 2002-TR-020, PA, USA:Software Engineering Institute.
42. Lindvall, M., Basili, V., Boehm, B., Costa, P., Dangle, K., Shull, F., Tesoriero, R., Williams, L., and Zelkowitz, M., 2002. Experical findings in Agile methods. Proceedings of Extreme Programming and Agile methods–XP/Agile Universe Chicago. 2002. pp. 197–207.
43. Lucas, H., 1982. Companion to Management Studies, London, UK:Heinemann Ltd.
44. Martin, R., 2003. Agile software development, Principles, patterns, and practices, NJ, USA:Prentice Hall.
45. Olson, D., and Stimmel, C., 2002. The manager pool, Patterns for radical leadership, NJ, USA:Addison-Wesley.
46. Orr, K., 2002. CMM versus Agile Development:Religious Wars and Software Development. Agile Project Management, 3 (7):1–29.
47. Pikkarainen, M., and Passoja, U., 2005. An approach for assessing suitability of Agile solutions:A case study. Proceedings of Extreme Programming and Agile processes in software engineering (XP 2005). 2005, Sheffield, UK.
48. Poole, C., and Huisman, J., 2001. Using extreme programming in a maintenance environment. IEEE Software, 18 (6):42–49.
49. Rasmusson, J., 2003. Introducing XP into Greenfield projects:Lessons learned. IEEE Software, 20 (3):21–28.
50. Reichheld, F., 2001. Lead for Loyalty. Harvard Business Review, 79 (7):76–84.
51. Reifer, D., 2002. “ How to get the most out of Extreme Programming/Agile methods ”. In Extreme Programming and Agile methods–XP/Agile Universe Chicago 185–196.
52. Rising, L., and Janoff, S., 2000. The scrum software development process for small teams. IEEE Software, 17 (4):26–32.
53. Rogers, E., 1962. Diffusion of Innovations, New York, USA:The Free Press.
54. Sammon, D., and Adam, F., 2004. “ Towards a Model of ERP Software Selection - Widening the Debate ”. In The Enterprise Resource Planning Decade:Lessons Learned and Issues for the Future, Edited by:Adam, F., and Sammon, D., Hershey, PS:Idea Publishing Group.
55. Stake, R., 2000. “ Case Studies ”. In The Handbook of Qualitative Research, Edited by:Denzin, N., and Lincoln, Y. S., 453–454. CA, USA:Sage Publications.
56. Stapleton, J., 2003. DSDM Business focused development, London, UK:Pearson Education.
57. Storey, J., 1983. Managerial Prerogative and the Question of Control, London, UK:Routledge&Kegan Paul.
58. Sutherl, J., 2001. Agile can scale:Inventing and Reinventing SCRUM in five companies. Cutter IT Journal, 14 (12):5–11.
59. th European Conference on Software Maintenance and Reengineering. 2005, Manchester, UK. pp. 256–264.
60. Swanson, E., 2001. “ Telling an innovation story ”. In Diffusing software product and process innovations, Edited by:Ardis, M., and Marcolin, B., 1–4. MA, USA:Kluwer Academic Publishers.
61. Swanson, E. B., and Ramiller, N. C., 2004. Innovating mindfully with information technology. MIS Quarterly, 28 (4):553–583.
62. th Pacific Asia Conference on Information Systems. 2004, Shanghai. pp. 458–471.
63. Turk, D., France, R., and Rumpe, B., 2005. Assumptions Underlying Agile Software-Development Processes. Journal of Database Management, 16 (4):62–87.
64. Williams, L., Kessler, R., Cunningham, W., and Jeffries, R., 2000. Strengthening the case for pairprogramming. IEEE Software, 17 (4):19–25.
65. Young, G., 2003. “ Implementing DSDM in eBA ”. In DSDM Business focused development, Edited by:Stapleton, J., 97–103. London, UK:Pearson Education.