This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
People over Process: Key Challenges in Agile Development
July/August 2011 (vol. 28 no. 4)
pp. 48-57
Kieran Conboy, National University of Ireland, Galway
Sharon Coyle, National University of Ireland, Galway
Minna Pikkarainen, VTT Technical Research Centre of Finland
There's a common perception that, although developers might experience some "teething" problems during the initial transition to agile methods, they're much happier, more engaged, and ultimately more productive with agile methods. However, this belief might not always hold true. Case studies identified many serious "people" challenges that 17 large multinational organizations experienced after using agile methods for more than three years. Challenges range from recruitment of agile staff to training, motivation, and performance evaluation. The studies produced a set of actionable recommendations on how organizations can overcome these challenges on the basis of better practices uncovered during the studies.

1. C.H. Tan and H.H. Teo, "Training Future Software Developers to Acquire Agile Development Skills," Comm. ACM, vol. 50, no. 12, 2007, pp. 97–98.
2. C. Poole and J.W. Huisman, "Using Extreme Programming in a Maintenance Environment," IEEE Software, vol. 18, no. 6, 2001, pp. 42–50.
3. J. Drobka, D. Noftz, and R. Raghu, "Piloting XP on Four Mission-Critical Projects," IEEE Software, vol. 21, no. 6, 2004, pp. 70–75.
4. D. Jamieson, K. Vinsen, and G. Callender, "Agile Procurement and Dynamic Value for Money to Facilitate Agile Software Projects," Proc. 32nd EuroMicro Conf. Software Eng. and Advanced Applications (EuroMicro 06), IEEE CS Press, 2006, pp. 248–255.
5. "DEEWR Tender Win," UXResearch, Sept. 2008; www.uxresearch.com.au/newsdeewr-tender-win.
6. S. Nerur, R. Mahapatra, and G. Mangalaraj, "Challenges of Migrating to Agile Methodologies," Comm. ACM, vol. 48, no. 5, 2005, pp. 72–78.
7. P. Schuh, Integrating Agile Development in the Real World, Charles River Media, 2004.
1. M.J. Gallivan, D.P. Truex, and L. Kvansy, "Changing Patterns in IT Skill Sets 1988-2003: A Content Analysis of Classified Advertising," ACM SIGMIS Database, vol. 35, no. 3, 2004, pp. 64-87.
2. M. Cohn and D. Ford, "Introducing an Agile Process to an Organization," Computer, vol. 36, no. 6, 2003, pp. 74-78.
3. A. Begel and N. Nagappan, "Usage and Perceptions of Agile Software Development in an Industrial Context: An Exploratory Study," Proc. 1st Int'l Symp. Empirical Software Eng. and Measurement (ESEM 07), IEEE CS Press, 2007, pp. 117-125.
4. D.S. Hovorka and K.R. Larsen, "Enabling Agile Adoption Practices through Network Organizations," European J. Information Systems, vol. 15, no. 2, 2006, pp. 159-168.
5. J.D. Becker, R.G. Insley, and M.L. Endres, "Communication Skills of Technical Professionals: A Report for Schools of Business Administration," ACM SIGCPR Computer Personnel, vol. 18, no. 2, 1997, pp. 3-19.
6. H.D. Crockett and C.J. Jeffries, "Preferred Information Systems Skills: Are Undergraduate IS Programs Serving Their Markets?" Interface, vol. 15, no. 2, 1993, pp. 9-13.
7. S. Cusack, "Moving Up to Management," Computerworld, vol. 22, no. 21, 1988, p. 82.
8. D.A. Fischer, "It's 2 P.M.: Do You Know Where Your Help Desk Is?" Infoworld, vol. 16, no. 24, 1994, p. 67.
9. C. Hildebrand, "Managing the Aftermath: Orchestration Skills Needed," Computerworld, vol. 25, no. 31, 1991, p. 58.
10. R.A. Pastore, "Decided Slant," CIO, vol. 7, no. 4, 1993, pp. 50-56.
11. B. Pitman, "Stop Wasting Training Dollars: Train for Outcomes, Not Outputs," J. Systems Management, vol. 44, no. 6, 1994, p. 25.
12. L.S. Ridgeway, "Read My Mind: What Users Want from Online Information," IEEE Trans. Professional Communications, vol. 30, no. 2, 1987, pp. 87-90.
13. P. Abrahamsson, "Commitment Nets in Software Process Improvement," Annals Software Eng., vol. 14, nos. 1-4, 2002, pp. 407-438.
14. R. Agarwal and J. Prasad, "A Field Study of the Adoption of Software Process Innovations by Information Systems Professionals," IEEE Trans. Eng. Management, vol. 47, no. 3, 2000, pp. 295-308.
15. L. Layman, L. Williams, and L. Cunningham, "Motivations and Measurements in an Agile Case Study," J. Systems Architecture, vol. 52, no. 11, 2006, pp. 654-667.
16. K. Petersen and C. Wohlin, "A Comparison of Issues and Advantages in Agile and Incremental Development between State of the Art and an Industrial Case," J. Systems and Software, vol. 82, no. 9, 2009, pp. 1479-1490.
17. S.C. Misra, V. Kumar, and U. Kumar, "Identifying Some Important Success Factors in Adopting Agile Software Development Practices," J. Systems and Software, vol. 82, no. 11, 2009, pp. 1869-1890.
18. R.L. Thompson, C.A. Higgins, and J.M. Howell, "Personal Computing: Toward a Conceptual Model of Utilization," MIS Q., vol. 15, no. 1, 1991, pp. 125-143.
19. A. Qumer and B. Henderson-Sellers, "A Framework to Support the Evaluation, Adoption and Improvement of Agile Methods in Practice," J. Systems and Software, vol. 81, no. 11, 2008, pp. 1899-1919.
20. J. Iivari and M. Huisman, "The Relationship between Organizational Culture and the Deployment of Systems Development Methodologies," MIS Q., vol. 31, no. 1, 2007, pp. 35-58.

Index Terms:
agile, agile software development, adoption, methodologies, people factors, developers, software development, software engineering
Citation:
Kieran Conboy, Sharon Coyle, Xiaofeng Wang, Minna Pikkarainen, "People over Process: Key Challenges in Agile Development," IEEE Software, vol. 28, no. 4, pp. 48-57, July-Aug. 2011, doi:10.1109/MS.2010.132
Usage of this product signifies your acceptance of the Terms of Use.