Agile systems development and stakeholder satisfaction: A South African empirical study

ACM International Conference Proceeding Series

Volumn 338, Issue , 2008, Pages 48-55

  Ferreira, Carlos ^a   Cohen, Jason ^b  

^a Business Systems Group (Africa)   (South Africa)

^b UNIVERSITY OF THE WITWATERSRAND   (South Africa)

Author keywords

Agile methods; Software development; Stakeholder satisfaction

Indexed keywords

AGILE METHODOLOGY; AGILE METHODS; BUSINESS ENVIRONMENTS; COLLECTIVE OWNERSHIP; DEVELOPMENT PROCESS; DEVELOPMENT PROJECT; EMPIRICAL RESEARCH; EMPIRICAL STUDIES; HIGH RATE; ITERATIVE DEVELOPMENT; RESEARCH MODELS; SOFTWARE DEVELOPMENT; STAKEHOLDER SATISFACTION; SYSTEMS DEVELOPMENT;

AGILE MANUFACTURING SYSTEMS; AMPLITUDE MODULATION; COMPUTER SOFTWARE; DIFFUSERS (OPTICAL); ENGINEERS; SOFTWARE DESIGN;

RESEARCH;

EID: 70049106135     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1456659.1456666     Document Type: Conference Paper

References (36)

1. Abrahamsson, P., Salo, O., Ronkainen, J., and Warsta, J. 2002. Agile Software Development Methods. Review and Analysis, VTT Publications, Finland.
2. Abrahamsson, P., Warsta, J., Siponen, M. T., and Ronkainen, J. 2003. New directions on agile methods: a comparative analysis. Proceedings of the International Conference on Software Engineering (Portland, Oregon, USA, May 03-05, 2003).
3. Aguanno, K. 2004. Managing Agile Projects, 1st Edition. Multi-Media Publications, Washington.
4. Alshayeb, M. and Li, W. 2005. An empirical study of system design instability metric and design evolution in an agile software process. J. Syst. Software. 74 (2005), 269-274.
5. Alshayeb, M. and Li, W. 2006. An empirical study of relationships among extreme programming engineering activities. Inform. Software Tech. 48 (2006),1068-1072.
6. Augustine, S., Payne, B., Sencindiver, F., and Woodcock, S. 2005. Agile project management: steering from the edges. Commun. ACM. 48,12 (2005), 85-89.
7. Baccarini, D. 1999. The logical framework method for defining project success. Project Management Journal. 30,4 (1999), 25-33.
8. Beck, K. 1999. Embracing Change with Extreme Programming. IEEE Computer. 32,10 (1999), 70-77.
9. Boehm, B. 2002. Get ready for agile methods, with care. IEEE Computer. 35,1 (2002), 64-69.
10. Capiluppi, A., Fernandez-Ramil, J., Higman, J., Sharp, H.C., and Smith, N. 2007. An empirical study of the evolution of an agile-developed software system. Proceedings of the 29th International Conference on Software Engineering (Minneapolis, MN, USA, 2007).
11. Crispin, L. 2006. Driving software quality: how test-driven development impacts software quality. IEEE Software. 23,6 (2006), 70-73.
12. Erickson, J., Lyytinen, K., and Siau, K. 2005. Agile modeling, agile software development, and extreme programming: the state of research. J. Database Manage. 16,4 (2005), 88-100.
13. Fitzgerald, B., Russo, N.L., and O'Kane, T. 2003. Software development method tailoring at Motorola. Commun. ACM. 46,4 (2003), 65-71
14. Fitzgerald, B., Hartnett, G., and Conboy, K. 2006. Customising agile methods to software practices at Intel Shannon. Eur. J. Inform. Syst. 15 (2006), 200-213.
15. Fruhling, A. and De Vreede, G-J. 2006. Field experiences with eXtreme programming: developing an emergency response system. J. Manage. Inform. Syst. 22,4 (2006), 39-68.
16. George, B. and Williams, L. 2004. A structured experiment of test-driven development. Inform. Software Tech. 46 (2004), 337-342.
17. Germain, E. and Robillard, P.N. 2005. Engineering-based processes and agile methodologies for software development: a comparative case study. J. Syst. Software. 75 (2005), 17-27.
18. Hansson, C., Dittrich, Y., Gustafsson, B., and Zarnak, S. 2006. How agile are industrial software development practices? J. Syst. Software. 79 (2006), 1295-1311.
19. Hedin, G., Bendix, L., and Magnusson, B. 2005. Teaching extreme programming to large groups of students. J. Syst. Software, 74 (2005), 133-146.
20. Highsmith, J. and Cockburn, A.A.R. 2001. Agile software development: the business of innovation. IEEE Computer. 34,9 (2001), 120-122.
21. Kim, H. and Pan, S.L. 2006. Towards a process model of information systems implementation : the case of customer relationship management (CRM). The DATA BASE for Advances in Information Systems. 37, 1 (Winter 2006), 59-76.
22. Kuppuswami, S. and Vivekanadan, K. 2004. The effects of pair programming on learning efficiency in short programming assignments. Informatics in Education. 3,2 (2004), 251-266.
23. Lindstrom, L. and Jeffries, R. 2004. Extreme programming and agile software development methodologies. Inform. Syst. Manage. 23,3 (2004), 41-52.
24. Manhart, P. and Scheider, K. 2004. Breaking the ice for agile development of embedded software: An industry experience report. Proceedings of the 26th International Conference of Software Engineering (San Diego, California, USA, 2004).
25. Martin, R. 2000. eXtreme programming development through dialog. IEEE Software. 17,4 (2000), 12-13.
26. McAnallen, M. and Coleman, G. 2005. Tailoring extreme programming for legacy systems: lessons learned. EuroSPI Conference (Budapest, Hungary, November 09 - 11, 2005).
27. McKeen, J.D., Guimaraes, T., and Wetherbe, J.C. 1994. The relationship between user participation and user satisfaction: an investigation of four contingency factors. MIS Quart. 18,4 (December 1994), 427-451.
28. Nerur, S., Mahapatra, R., and Mangalaraj, G. 2005. Challenges in migrating to agile methodologies. Commun. ACM. 48,5 (2005), 72-78.
29. Pitts, M.G. and Browne, G.J. 2007. Improving requirements elicitation: an empirical investigation of procedural prompts. Inform. Syst. J. 17 (2007), 89-110.
30. Sambamurthy, V., Bharadwaj, A., and Grover, V. 2003. Shaping agility through digital options: reconceptualizing the role of information technology in contemporary firms. MIS Quart. 27,2 (2003), 237-263.
31. Schneider, J-G. and Johnston, L. 2005. eXtreme Programming-helpful or harmful in educating undergraduates? J. Syst. Software. 74 (2005), 121-132.
32. Strong, K. C., Ringer, R.C., and Taylor, S.A. 2001. The* rules of stakeholder satisfaction (*timeliness, honesty and empathy). J. Bus. Ethics. 32,3 (2001), 219-231.
33. Turk, D., France, R., and Rumpe, B. 2005. Assumptions underlying agile software-development processes. J. Database Manage. 16,4 (Oct-Dec 2005), 62-87.
34. Turner, J.R. 2002. The project Manager as change agent. Proceedings of the Australian institute for Project Management (AIPM) Conference (Sydney, Australia, 2002).
35. Vanderburg, G. 2005. A simple model of agile software processes -or- extreme programming annealed. Proceedings of the 20th Annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications (San Diego, California, USA, October 16-20, 2005).
36. Williams, L. and Cockburn, A. 2003. Agile software development: it's about feedback and change. IEEE Computer. 36,6 (2003), 39-43.