People over process: key people challenges in agile development

This article has been accepted for publication in IEEE Software but has not yet been fully edited. Some content may change prior to final publication. Abstract: There is a common perception that, while there may be some 'teething' problems experienced during the initial transition to agile, people are much happier, engaged and ultimately more productive in these environments. This study shows that this belief may not always hold true, identifying many serious 'people' challenges experienced by 17 large multinational organisations, all using agile for more than three years. The cases provide an interesting insight in that they involve instances where agile was implemented in a top-down manner across the organisations or at least across business units. This is in contrast to most accounts of agile which involve voluntary, bottom up adoption on small co-located teams developing systems deemed to be suitable for agile development. The people issues uncovered include a broad range of problems from recruitment of agile staff, to training, motivation and performance evaluation among others. The paper will conclude with a set of actionable recommendations as to how organisations can overcome these challenges, based on the better practices uncovered in the cases studied.

[1]  Robert G. Insley,et al.  Communication skills of technical professionals: a report for schools of business administration , 1997, CPRS.

[2]  Ritu Agarwal,et al.  A field study of the adoption of software process innovations by information systems professionals , 2000, IEEE Trans. Engineering Management.

[3]  Brian Henderson-Sellers,et al.  A framework to support the evaluation, adoption and improvement of agile methods in practice , 2008, J. Syst. Softw..

[4]  Jane M. Howell,et al.  Personal Computing: Toward a Conceptual Model of Utilization , 1991, MIS Q..

[5]  Peter Schuh Integrating Agile Development In The Real World , 2004 .

[6]  Claes Wohlin,et al.  A comparison of issues and advantages in agile and incremental development between state of the art and an industrial case , 2009, J. Syst. Softw..

[7]  Lynette Kvasny,et al.  Changing patterns in IT skill sets 1988-2003: a content analysis of classified advertising , 2004, DATB.

[8]  Jerry Drobka,et al.  Piloting XP on four mission-critical projects , 2004, IEEE Software.

[9]  Andrew Begel,et al.  Usage and Perceptions of Agile Software Development in an Industrial Context: An Exploratory Study , 2007, ESEM 2007.

[10]  L. S. Ridgeway Read my mind: What users want from online information , 1987, IEEE Transactions on Professional Communication.

[11]  George Mangalaraj,et al.  Challenges of migrating to agile methodologies , 2005, CACM.

[12]  Dirk S. Hovorka,et al.  Enabling agile adoption practices through network organizations , 2006, Eur. J. Inf. Syst..

[13]  Vinod Kumar,et al.  Identifying some important success factors in adopting agile software development practices , 2009, J. Syst. Softw..

[14]  Diane Jamieson,et al.  Agile Procurement and Dynamic Value for Money to Facilitate Agile Software Projects , 2006, 32nd EUROMICRO Conference on Software Engineering and Advanced Applications (EUROMICRO'06).

[15]  Mike Cohn,et al.  Introducing an Agile Process to an Organization , 2003, Computer.

[16]  Charles J. Poole,et al.  Using Extreme Programming in a Maintenance Environment , 2001, IEEE Softw..

[17]  Lucas Layman,et al.  Motivations and measurements in an agile case study , 2006, J. Syst. Archit..

[18]  Juhani Iivari,et al.  The Relationship Between Organisational Culture and the Deployment of Systems Development Methodologies , 2001, CAiSE.

[19]  Chuan-Hoo Tan,et al.  Training future software developers to acquire agile development skills , 2007, CACM.

[20]  Pekka Abrahamsson,et al.  Commitment Nets in Software Process Improvement , 2002, Ann. Softw. Eng..