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  2007 John Wiley & Sons, Ltd.

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

[2]  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..

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

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

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

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

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

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

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

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

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

[12]  E. Rogers,et al.  Diffusion of innovations , 1964, Encyclopedia of Sport Management.

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

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

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

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

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

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

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

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

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

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

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

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

[25]  Roger Schwarz,et al.  The Skilled Facilitator , 1994 .

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

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

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

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

[30]  语言学和文学.  European Journal of Information Systems , 2010 .

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

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

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

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

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

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

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

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

[39]  Doris L. Carver,et al.  TRANSACTIONS ON SOFTWARE ENGINEERING , 2004 .

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

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

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

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

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