Identifying some important success factors in adopting agile software development practices

Journal of Systems and Software

Volumn 82, Issue 11, 2009, Pages 1869-1890

  Misra, Subhas Chandra ^a   Kumar, Vinod ^b   Kumar, Uma ^b  

^a INDIAN INSTITUTE OF TECHNOLOGY KANPUR   (India)

^b CARLETON UNIVERSITY   (Canada)

Author keywords

Agile software; Success factors

Indexed keywords

AGILE SOFTWARE DEVELOPMENT; AGILE SOFTWARES; CORPORATE CULTURE; CUSTOMER COLLABORATION; DATA ANALYSIS; DATA ANALYSIS TECHNIQUES; DECISION TIME; PERSONAL CHARACTERISTICS; RESEARCH METHODOLOGIES; RESEARCH QUESTIONS; SOFTWARE DEVELOPMENT; SUCCESS FACTORS;

CUSTOMER SATISFACTION; DATA HANDLING; FLUORINE CONTAINING POLYMERS; RESEARCH; SALES; SOFTWARE DESIGN; SURVEYS;

COMPUTER SOFTWARE;

EID: 71749097189     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.jss.2009.05.052     Document Type: Article

References (69)

1. Abrahamsson, P., Salo, O., Ronkainen, J., 2002. Agile Software Development Methods - Review and Analysis. VTT Publications 478. (accessed December 2005).
2. Abrahamsson, P., Koskela, J., 2004. Extreme programming: a survey of empirical data from a controlled case study. In: Proceedings of the 2004 International Symposium on Empirical Software Engineering (ISESE'04). Redondo Beach, California, USA, pp. 73-92.
3. Ambler, S.W., 2005a. Communication on Agile Software Projects. Online article that can be found at http://www.agilemodeling.com/essays/communication.htm (accessed December 2005).
4. Ambler, S.W., 2005b. Remaining Agile. Online article that can be found at http://www.agilemodeling.com/essays/remainingAgile.htm (accessed December 2005).
5. Ambler S. Quality in an agile world. Software Quality Professional 7 4 (2005) 34-40
6. Anderson, D., 2002. Morning Roll Call. (accessed 04.03.07).
7. Baheti, P., Williams, L., Gehringer, E., Stotts, D., Smith, J.M., 2002. Distributed Pair Programming: Empirical Studies and Supportive Environments. Technical Report TR02-010. Department of Computer Science, University of North Carolina at Chapel Hill.
8. Baskerville R., Ramesh B., Levine L., Pries-Heje J., and Slaughter S. Is internet-speed software development different. IEEE Software 20 6 (2003) 70-77
9. Boehm B. Software Engineering Economics (1981), Prentice Hall
10. Boehm, B., Turner, R., 2003. Observations on balancing discipline and agility. In: Proceedings of the Agile Development Conference (ADC'03). Salt Lake City, Utah, USA.
11. Boehm B., and Turner R. Management challenges to implementing agile processes in traditional development organizations. IEEE Software (2005) 30-39
12. Bossavit L. The unbearable lightness of programming: a tale of two cultures. Cutter IT Journal 15 9 (2002) 5-11
13. Ceschi M., Sillitti A., Succi G., and De Panfilis D. Project management in plan-based and agile companies. IEEE Software 22 3 (2005) 21-27
14. Chong, J., 2005. Social behaviors on XP and non-XP teams: a comparative study. In: Proceedings of the Agile Development Conference (ADC'05).
15. Cockburn A. Agile Software Development. first ed. (2001), Addison-Wesley
16. Cockburn, A., 2002. Learning from agile software development - Part 1. CrossTalk: Journal of Defense Software Engineering. .
17. Cockburn A. Learning from agile software development - Part 2. CrossTalk: Journal of Defense Software Engineering (2002) 9-12
18. Cockburn A., and Highsmith J. Agile software development: the people factor. Software Management (2001) 131-133
19. Cohn M., and Ford D. Introducing an agile process to an organization. IEEE Computer (2003) 74-78
20. Copeland, L., 2001. Developers approach extreme programming with caution. Computerworld, October 22. (accessed 04.03.07).
21. Dagnino, A., Smiley, K., Srikanth, H., Anton, A.I., Williams, L., 2004. Experiences in applying agile software development practices in new product development. In: Proceedings of the 8th IASTED International Conference on Software Engineering and Applications, November 9-11, Cambridge, MA, USA.
22. Dalcher, D., Benediktsson, O., Thorbergsson, H., 2005. Development lifecycle management: a multi-project experiment. In: Proceedings of the 12th International Conference and Workshops on the Engineering of Computer-Based Systems (ECBS'05).
23. Deias, R., Mugheddo, G., Murro, O., 2002. Introducing Agile in a Startup. (accessed 04.03.07).
24. Dingsoyr T., and Hansen G.K. Extending agile methods: postmortem reviews as extended feedback. Lecture Notes in Computer Science 2630 (2004) 4-12
25. Drobka J., Noftz D., and Raghu R. Piloting XP on four mission-critical projects. IEEE Software (2004) 70-75
26. Dybå T. An instrument for measuring the key factors for success in software process improvement. Empirical Software Engineering 5 4 (2000) 357-390
27. Dybå T. Improvisation in small software organizations. IEEE Software 17 5 (2000) 82-87
28. Dybå, T., 2003. Factors for software process improvement success in small and large organizations: an empirical study in the Scandinavian context. In: Proceedings of the Joint Ninth European Software Engineering Conference (ESEC) and 11th SIGSOFT Symposium on Foundations in Software Engineering (FSE-11), pp. 148-157.
29. Dybå T. An empirical investigation of the key factors for success in software process improvement. IEEE Transactions on Software Engineering 31 5 (2005) 410-424
30. Dybå T., and Dingsøyr T. Empirical studies of agile software development: a systematic review. Information and Software Technology 50 9-10 (2008) 833-859
31. El Eman K., Fusaro P., and Smith B. Success factors and barriers for software process improvement. In: Messnarz R., and Tully C. (Eds). Better Software Practice for Business Benefit: Principles and Experience (1999), CS Press 355-371
32. Fowler, M., Highsmith, J., 2001. The Agile Manifesto. Software Development Magazine. (accessed December 2005).
33. Fowler, M., 2002. The Agile Manifesto: Where It Came From and Where It May Go. (accessed December 2005).
34. Fowler, M., 2006. Using an Agile Software Development Process with Offshore Development. (accessed 04.03.07).
35. Goldenson, D.R., Herbsleb, J.D., 1995. After the Appraisal: A Systematic Survey of Process Improvement, its Benefits and Factors that Influence Success. Technical Report. CMU/SEI-95-TR-009, SEI, Carnegie Mellon University.
36. Graffin, L.A., 2001. A Customer Experience: Implementing XP. (accessed 04.03.07).
37. Harrison, N.B., 2003. A Study of Extreme Programming in a Large Company. (accessed 04.03.07).
38. Jensen, O., 2002. Time Constrained Requirements Engineering - The Cooperative Way. (accessed 04.03.07).
39. Jokela, T., Abrahamsson, P., 2004. Usability assessment of an extreme programming project: close cooperation with the customer does not equal to good usability. Product Focused Software Process Improvement, Lecture Notes in Computer Science, vol. 3009. Springer-Verlag, Berlin, pp. 393-407.
40. Karlstroem D., and Runeson P. Combining agile methods with stage-gate project management. IEEE Software 22 3 (2005) 43-49
41. Keith, E.R., 2002. Agile Software Development Processes: A Different Approach to Software Design. (accessed December, 2005).
42. Layman, L., Williams, L., Cunningham, L., 2004. Exploring extreme programming in context: an industrial case study. In: Proceedings of the Agile Development Conference (ADC'04).
43. Lindvall, M., Basili, V., Boehm, B., Costa, P., Dangle, K., Shull, F., Tesoriero, R., Williams, L., Zelkowitz, M., 2002. Empirical findings in agile methods. In: Proceedings of Extreme Programming and Agile Methods - XP/Agile Universe 2002, pp. 197-207.
44. Macias, F., Holcombe, M., Gheorghe, M., 2003. A formal experiment comparing extreme programming with traditional software construction. In: Proceedings of the 4th Mexican International Conference on Computer Science (ENC 2003).
45. Mann, C., Maurer, F., 2005. A case study on the impact of scrum on overtime and customer satisfaction. In: Proceedings of Agile Development Conference (ADC'05).
46. Mannaro, K., Melis, M., Marchesi, M., 2004. Empirical analysis on the satisfaction of IT employees comparing XP practices with other software development methodologies. In: Proceedings of Extreme Programming and Agile Processes in Software Engineering, LNCS, vol. 3092. Springer-Verlag, pp. 166-174.
47. McMahon, P.E., 2004. Bridging agile and traditional development methods: a project management perspective. CrossTalk: The Journal of Defense Software Engineering. (accessed December 2005).
48. Melnik, G., Maurer, F., 2002. Perceptions of agile practices: a student survey. In: Proceedings of Extreme Programming/Agile Universe 2002. Lecture Notes in Computer Science, vol. 2418. Springer-Verlag, pp. 241-250.
49. Middleton P. Lean software development: two case studies. Software Quality Journal 9 4 (2001) 241-252
50. Nerur S., Mahapatra R., and Mangalaraj G. Challenges of migrating to agile methodologies. Communications of the ACM 48 5 (2005) 73-78
51. Opperthauser, D., 2003. Defect management in an agile development environment. CrossTalk: The Journal of Defense Software Engineering. (accessed December 2005).
52. Pine, S.M., 2001. An Application of XP in a Multiple Team/Multi-Process Environment. (accessed December 2005).
53. Parrish A., Smith R., Hale D., and Hale J. A field study of developer pairs: productivity impacts and implications. IEEE Software 21 5 (2004) 76-79
54. PMI, 2004. Project Management Body of Knowledge (PMBOK). third ed. Project Management Institute. USA.
55. Reiffer D.J. How good are agile methods?. IEEE Software (2002) 14-17
56. Rainer A., and Hall T. Key success factors for implementing software process improvement: a maturity-based analysis. Journal of Systems and Software 62 2 (2002) 71-84
57. Robinson, H., Sharp, H., 2004. The characteristics of XP teams. In: Extreme Programming and Agile Processes in Software Engineering, Lecture Notes in Computer Science, vol. 3092. Springer-Verlag, Berlin, pp. 139-147.
58. Rumpe, B., Schroder, A., 2002. Quantitative survey on extreme programming projects. In: Proceedings of International Conference on Extreme Programming and Flexible Processes in Software Engineering (XP2002) Alghero, Italy, pp. 95-100.
59. Salo O., and Abrahamsson P. Agile methods in European embedded development organizations: a survey study of extreme programming and scrum. IET Software 2 1 (2008) 58-64
60. Schwaber K., and Beedle M. Agile Software Development with Scrum (2002), Prentice Hall, New Jersey, USA
61. Sharp H., and Robinson H. An ethnographic study of XP practice. Empirical Software Engineering 9 4 (2004) 353-375
62. Shine Technologies, 2003. Agile Methodologies: Survey Results. Shine Technologies Pty Ltd. (accessed December 2005).
63. Sillitti, A., Ceschi, M., Russo, B., Succi, G., 2005. Managing uncertainty in requirements: a survey in documentation driven and agile companies. In: Proceedings of the 11th International Software Metrics Symposium (METRICS 2005).
64. Stelzer D., and Mellis W. Success factors of organization change in software process improvement. Software Process - Improvement and Practice 4 4 (1998) 227-250
65. Turk, D., France, R., Rumpe, B., 2002. Limitations of agile software processes. In: Proceedings of the 3rd International Conference on Extreme Programming and Agile Processes in Software Engineering. Sardinia, Italy.
66. Turner R., and Boehm B. People factors in software management: lessons from comparing agile and plan driven methods. CrossTalk: The Journal of Defense Software Engineering (2003) 4-8
67. Wellington, C.A., Briggs, T., Girard, C.D., 2005. Comparison of student experiences with plan driven and agile methodologies. In: Proceedings of the 35th ASEE/IEEE Frontiers in Education Conference.
68. Young, S.M., Edwards, H.M., Mcdonald, S., Thompson, J.B., 2005. Personality characteristics in an XP team: a repertory grid study. In: Proceedings of the Human and Social Factors of Software Engineering (HSSE), St. Louis, MI, USA.
69. Yusof S.M., and Aspinwall E. Critical success factors for total quality management implementation in small and medium enterprises. Total Quality Management 10 4-5 (1999) 803-809