Exploring Win-Win Contracts: An Appreciative Inquiry into IT Project Management

IT project management research largely adopts a negative approach with an emphasis on risks, problems, and failures. Although that approach has led to important theoretical and practical insights, this study adopts a positive approach to explore complementary ways to improve current practices. Accordingly, we report from a small software firm, TelSoft, in which we applied Appreciative Inquiry (AI) to identify “win-win contracts” as a generative metaphor for IT project management and to develop action strategies to manage scope, time, cost, and quality in TelSoft’s IT projects. As a contribution to the IT project management literature, we show how the generative metaphor and related action strategies were developed at TelSoft and discuss relationships to existing theory—most notably Theory W. In addition, as a contribution to the participatory change literature within the Information Systems discipline, we show how AI and the four steps of initiating, inquiring, imagining, and innovating were applied at TelSoft to learn about existing strengths in IT project management and to improve current practices through a series of workshops for project managers. We present the AI process in detail and discuss our experiences in relation to other approaches to participatory change.

[1]  Ashley A. Bush,et al.  Reconciling user and project manager perceptions of IT project risk: a Delphi study 1 , 2002, Inf. Syst. J..

[2]  David L. Cooperrider,et al.  Appreciative inquiry handbook : the first in a series of AI workbooks for leaders of change , 2005 .

[3]  Kim Halskov Madsen,et al.  A guide to metaphorical design , 1994 .

[4]  Gondy Leroy,et al.  Requirements engineering using appreciative inquiry for an online community of caregivers of children with autism , 2009, SAC '09.

[5]  Kathy Schwalbe,et al.  Information Technology Project Management , 1999 .

[6]  Vijay K. Vaishnavi,et al.  Facilitating experience reuse among software project managers , 2008, Inf. Sci..

[7]  Trevor Wood-Harper,et al.  Multiview - An Exploration in Information Systems Development , 1986, Aust. Comput. J..

[8]  J. Landry,et al.  The Power of Appreciative Inquiry , 2003 .

[9]  Sune Dueholm Müller,et al.  Improvement as organizational change : A metaphorical nalysis of the literature une , 2010 .

[10]  Michael E. Fagan Advances in software inspections , 1986, IEEE Transactions on Software Engineering.

[11]  Bob McFeeley,et al.  IDEAL: A User's Guide for Software Process Improvement. , 1996 .

[12]  Lars Mathiassen,et al.  Information-centric assessment of software metrics practices , 2005, IEEE Transactions on Engineering Management.

[13]  Mary Beth Rosson,et al.  Beyond being aware , 2009, Inf. Organ..

[14]  Robert M. Davison,et al.  Empowerment or enslavement?: A case of process-based organisational change in Hong Kong , 2002, Inf. Technol. People.

[15]  David L. Cooperrider Appreciative inquiry : an emerging direction for organization development , 2001 .

[16]  Vijay K. Vaishnavi,et al.  Five Keys to Project Knowledge Sharing , 2007, IT Professional.

[17]  Jan Pries-Heje,et al.  Internet Software Engineering: A Different Class of Processes , 2002, Ann. Softw. Eng..

[18]  Peter Checkland,et al.  Systems Thinking, Systems Practice , 1981 .

[19]  Kweku Ewusi-Mensah,et al.  Software development failures : anatomy of abandoned projects , 2003 .

[20]  H. Preskill,et al.  An overview of appreciative inquiry in evaluation , 2003 .

[21]  Kalle Lyytinen,et al.  Identifying Software Project Risks: An International Delphi Study , 2001, J. Manag. Inf. Syst..

[22]  Tom DeMarco,et al.  Controlling Software Projects: Management, Measurement, and Estimates , 1986 .

[23]  Gondy Leroy,et al.  Eliciting user requirements using Appreciative inquiry , 2011, Empirical Software Engineering.

[24]  Tuure Tuunanen,et al.  A Contigency Model for Requirements Development , 2007, J. Assoc. Inf. Syst..

[25]  Heinz K. Klein,et al.  Open and free deliberation: A prerequisite for positive design , 2009, Inf. Organ..

[26]  A. Pettigrew Context and Action in the Transformation of the Firm , 1987 .

[27]  Robert W. Zmud,et al.  A Contingency Approach to Software Project Coordination , 2002, J. Manag. Inf. Syst..

[28]  Barry W. Boehm,et al.  Theory-W Software Project Management: Principles and Examples , 1989, IEEE Trans. Software Eng..

[29]  Kalle Lyytinen,et al.  Learning failure in information systems development , 1999, Inf. Syst. J..

[30]  Robert M. Davison,et al.  Principles of canonical action research , 2004, Inf. Syst. J..

[31]  J. Hackman,et al.  Total Quality Management: Empirical, Conceptual, and Practical Issues , 1995 .

[32]  Jeremy Rose,et al.  Prescription, description, reflection: the shape of the software process improvement field , 2004, Int. J. Inf. Manag..

[33]  Blaize Horner Reich,et al.  The impact of size and volatility on IT project performance , 2007, CACM.

[34]  Lars Mathiassen,et al.  Systems Development and Trade Union Activities , 1980 .

[35]  Agneta Nilsson,et al.  Appreciating Lessons Learned , 2010, IEEE Software.

[36]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[37]  Sheila Simsarian Webber,et al.  Project managers doubling as client account executives , 2004 .

[38]  Nannette P. Napier,et al.  Building contextual ambidexterity in a software company to improve firm-level coordination , 2011, Eur. J. Inf. Syst..

[39]  Barry W. Boehm,et al.  Software requirements as negotiated win conditions , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[40]  APPRECIATIVE INQUIRY IN THE OFFICE OF RESEARCH AND DEVELOPMENT: Improving the Collaborative Capacity of Organization , 2006 .

[41]  Richard Baskerville,et al.  Diversity in information systems action research methods , 1998 .

[42]  Steve McConnell Software Estimation: Demystifying the Black Art , 2006 .

[43]  Frank J. Barrett,et al.  Generative Metaphor Intervention: A New Approach for Working with Systems Divided by Conflict and Caught in Defensive Perception , 1990 .

[44]  Barry W. Boehm,et al.  Applying WinWin to quality requirements: a case study , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[45]  Lars Mathiassen,et al.  Contextual dynamics during health information systems implementation: an event-based actor-network approach , 2008, Eur. J. Inf. Syst..

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

[47]  Genaro J. Gutierrez,et al.  Parkinson's Law and Its Implications for Project Management , 1991 .

[48]  Lars Mathiassen,et al.  The post mortem paradox: a Delphi study of IT specialist perceptions , 2008, Eur. J. Inf. Syst..

[49]  R. Fisher,et al.  Getting to Yes: Negotiating Agreement Without Giving in , 1981 .

[50]  Kalle Lyytinen,et al.  Design With a Positive Lens: An Affirmative Approach to Designing Information and Organizations , 2006, Commun. Assoc. Inf. Syst..

[51]  Stephen H. Haeckel Adaptive enterprise design: The sense‐and‐respond model , 1995 .

[52]  C. Elliot Locating the Energy for Change: An Introduction to Appreciative Inquiry , 1999 .

[53]  Anna Börjesson Sandberg,et al.  Appreciative inquiry in software process improvement , 2009 .

[54]  Kalle Lyytinen,et al.  Introduction to designing information and organizations with a positive lens , 2009, Inf. Organ..

[55]  Fred H. Blum,et al.  Action Research--A Scientific Approach? , 1955, Philosophy of Science.

[56]  Building a Win-Win World: Life Beyond Global Economic Warfare , 1996 .

[57]  Lars Mathiassen,et al.  Collaborative Practice Research , 2000, Scand. J. Inf. Syst..

[58]  G. R. Bushe,et al.  When Is Appreciative Inquiry Transformational? , 2005 .

[59]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.

[60]  Barry Boehm,et al.  A collaborative spiral software process model based on Theory W , 1994, Proceedings of the Third International Conference on the Software Process. Applying the Software Process.

[61]  Adrian J. Slywotzky,et al.  Adaptive Enterprise: Creating and Leading Sense-And-Respond Organizations , 1999 .

[62]  Mark Keil,et al.  Reporting bad news on software projects: the effects of culturally constituted views of face‐saving , 2007, Inf. Syst. J..

[63]  Enid Mumford,et al.  Computer systems in work design--the ETHICS method : effective technical and human implementation of computer systems , 1979 .

[64]  Lars Mathiassen,et al.  Improving software organizations: agility challenges and implications , 2005, Inf. Technol. People.

[65]  Jan Pries-Heje,et al.  Making IT Project De-Escalation Happen: An Exploration into Key Roles , 2008, J. Assoc. Inf. Syst..

[66]  Jurgen Faust Positive design , 2009 .

[67]  Lynn Crawford,et al.  Fundamental uncertainties in projects and the scope of project management , 2006 .

[68]  Mike Chiasson,et al.  Pluralist action research: a review of the information systems literature * , 2009, Inf. Syst. J..

[69]  Nannette P. Napier,et al.  Negotiating Response-ability and Repeat-ability in Requirements Engineering , 2006, ICIS.

[70]  Rikard Lindgren,et al.  Design Principles for Competence Management Systems: A Synthesis of an Action Research Study , 2004, MIS Q..

[71]  Julie E. Kendall,et al.  Metaphors and Methodologies: Living Beyond the Systems Machine , 1993, MIS Q..

[72]  M. Rosenzweig,et al.  Win-Win Ecology: How the Earth's Species Can Survive in the Midst of Human Enterprise , 2003 .

[73]  Michael Fagan Design and Code Inspections to Reduce Errors in Program Development , 1976, IBM Syst. J..

[74]  G. Susman,et al.  An Assessment of the Scientific Merits of Action Research. , 1978 .

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

[76]  Jeff Sutherland,et al.  Manifesto for Agile Software Development , 2013 .

[77]  A. Pettigrew Longitudinal Field Research on Change: Theory and Practice , 1990 .

[78]  Mark Keil,et al.  Pulling the Plug: Software Project Management and the Problem of Project Escalation , 1995, MIS Q..

[79]  Jeremy Rose,et al.  Interaction, transformation and information systems development - an extended application of Soft Systems Methodology , 2002, Inf. Technol. People.

[80]  Nannette P. Napier,et al.  Combining Perceptions and Prescriptions in Requirements Engineering Process Assessment: An Industrial Case Study , 2009, IEEE Transactions on Software Engineering.

[81]  Ivan Rozman,et al.  Managing the complexity of SPI in small companies , 2000 .

[82]  Kalle Lyytinen,et al.  Components of Software Development Risk: How to Address Them? A Project Manager Survey , 2000, IEEE Trans. Software Eng..

[83]  Peter Checkland,et al.  Soft Systems Methodology: a 30-year retrospective , 1999 .

[84]  Nannette P. Napier,et al.  A study of reported practical experiences about TSP implementations , 2008 .

[85]  Victor R. Basili,et al.  A meta-model for software development resource expenditures , 1981, ICSE '81.

[86]  J. Alexander,et al.  Images of Organization , 1988 .

[87]  Frederick D. Lazar,et al.  Project Partnering: Improving the Likelihood of Win/Win Outcomes , 2000 .

[88]  Bernard C. Y. Tan,et al.  A Cross-Cultural Study on Escalation of Commitment Behavior in Software Projects , 2000, MIS Q..

[89]  G. Lakoff,et al.  Metaphors We Live By , 1980 .

[90]  D. Schoen The Reflective Practitioner , 1983 .

[91]  Steve McConnell,et al.  Software Project Survival Guide , 1997 .

[92]  Alan M. Davis,et al.  A Unified Model of Requirements Elicitation , 2004, J. Manag. Inf. Syst..