Preparing small software companies for tailored agile method adoption: Minimally intrusive risk assessment

There is often a misconception that adopting and tailoring agile methods is straightforward resulting in improved products and increasingly satisfied customers. However, the empirical nature of agile methods means that potential practitioners need to carefully assess whether they are exposed to the risks that can make agile method adoption problematic. This is particularly the case with small software companies who are less able to absorb the impact of failed experimentation. This study describes a minimally intrusive assessment approach for small software companies preparing for agile method adoption and tailoring in the light of key risks. The approach has been conducted with six small software companies, three of which are presented to show the evolution of the approach, describe the resource commitment that companies have to make, and highlight the type of information generated from an assessment. The contribution of this study is that small software companies have an alternative to ‘mere experimentation’ with agile methods and can take reasoned steps towards their adoption and tailoring. Copyright © 2008 John Wiley & Sons, Ltd.

[1]  Victor R. Basili,et al.  Iterative and incremental developments. a brief history , 2003, Computer.

[2]  Eric Overby,et al.  Enterprise agility and the enabling role of information technology , 2006, Eur. J. Inf. Syst..

[3]  Barry W. Boehm,et al.  Using Risk to Balance Agile and Plan-Driven Methods , 2003, Computer.

[4]  Per Runeson,et al.  Integrating agile software development into stage-gate managed product development , 2006, Empirical Software Engineering.

[5]  Marian Gheorghe,et al.  The Impact of an Agile Methodology on the Well Being of Development Teams , 2006, Empirical Software Engineering.

[6]  Weidong Xia,et al.  The ability of information systems development project teams to respond to business and technology changes: a study of flexibility measures , 2005, Eur. J. Inf. Syst..

[7]  Barry Boehm,et al.  Balancing Agility and Dis-cipline: A Guide for the Perplexed , 2003 .

[8]  David L. Cooperrider,et al.  Appreciative Inquiry: A Positive Revolution in Change , 2005 .

[9]  ToMarshall Egan,et al.  Comparing Appreciative Inquiry to Action Research: OD Practitioner Perspectives , 2005 .

[10]  Mark Keil,et al.  Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models , 2000, MIS Q..

[11]  Pekka Abrahamsson,et al.  New directions on agile methods: a comparative analysis , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[12]  Trevor Wood-Harper,et al.  A critical perspective on action research as a method for information systems research , 1996, J. Inf. Technol..

[13]  E. Rogers.  Diffusion of Innovations , 1962 .

[14]  Alberto Sillitti,et al.  Project management in plan-based and agile companies , 2005, IEEE Software.

[15]  W. W. Royce,et al.  Managing the development of large software systems , 1970 .

[16]  Stanley M. Sutton.  The Role of Process in a Software Start-up , 2000, IEEE Softw..

[17]  Lars Mathiassen,et al.  Managing Risk in Software Process Improvement: An Action Research Approach , 2004, MIS Q..

[18]  Anthony F. Buono,et al.  RETHINKING ORGANIZATIONAL CHANGE: Reframing the Challenge of Change Management , 2005 .

[19]  Jim Highsmith,et al.  Agile Software Development Ecosystems , 2002 .

[20]  Des Greer,et al.  Applying an Agility/Discipline Assessment for a Small Software Organisation , 2006, PROFES.

[21]  Barry W. Boehm,et al.  Rebalancing Your Organization's Agility and Discipline , 2003, XP/Agile Universe.

[22]  Sylvie Trudel,et al.  PEM: The small company-dedicated software process quality evaluation method combining CMMISM and ISO/IEC 14598 , 2006, Software Quality Journal.

[23]  Yvonne Dittrich,et al.  How agile are industrial software development practices? , 2006, J. Syst. Softw..

[24]  Fergal McCaffery,et al.  Adept: A Unified Assessment Method for Small Software Companies , 2007, IEEE Software.

[25]  Geoff Walsham,et al.  Doing interpretive research , 2006, Eur. J. Inf. Syst..

[26]  R. Yin.  Case Study Research: Design and Methods , 1984 .

[27]  Geoffrey A. Moore,et al.  Inside the Tornado: Marketing Strategies from Silicon Valley's Cutting Edge , 1995 .

[28]  Tetsuo Tamai,et al.  Framework for matching requirements elicitation techniques to project characteristics , 2006, Softw. Process. Improv. Pract..

[29]  Geoffrey A. Moore.  Crossing the chasm : marketing and selling technology products to mainstream customers , 1991 .

[30]  Anthony S. White,et al.  External disturbance control for software project management , 2006 .

[31]  Hallie Preskill,et al.  Reframing Evaluation Through Appreciative Inquiry , 2006 .

[32]  Geoff Walsham,et al.  Interpretive case studies in IS research: nature and method , 1995 .

[33]  Brian Fitzgerald,et al.  Customising agile methods to software practices at Intel Shannon , 2006, Eur. J. Inf. Syst..

[34]  Magne Jørgensen,et al.  A comparison of software project overruns - flexible versus sequential development models , 2005, IEEE Transactions on Software Engineering.

[35]  Barry W. Boehm,et al.  Get Ready for Agile Methods, with Care , 2002, Computer.

[36]  Anna Börjesson Sandberg,et al.  Agile improvement practices in software organizations , 2006, Eur. J. Inf. Syst..

[37]  Ken Schwaber,et al.  Agile Project Management with Scrum , 1980 .

[38]  Andreas Rüping,et al.  Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects , 2003 .

[39]  Richard Baskerville,et al.  Generalizing Generalizability in Information Systems Research , 2003, Inf. Syst. Res..

[40]  Mark Keil,et al.  Why software projects escalate: the importance of project management constructs , 2003, IEEE Trans. Engineering Management.

[41]  Tore Dybå,et al.  An empirical investigation of the key factors for success in software process improvement , 2005, IEEE Transactions on Software Engineering.

[42]  Mike Crone,et al.  The Irish Indigenous Software Industry: Explaining the Development of a Knowledge-intensive Industry Cluster in a Less Favoured Region , 2002 .

[43]  George Wilkie,et al.  Northern Ireland Software Industry Survey , 2004 .

[44]  Jos van Hillegersberg,et al.  Change factors requiring agility and implications for IT , 2006, Eur. J. Inf. Syst..