A Paradox of Virtual Teams and Change: An Implementation of the Theory of Competing Commitments

International Journal of e-Collaboration (IJeC)

Volumn 2, Issue 3, 2006, Pages 1-24

  Mcavoy, John ^a   Butler, Tom ^a  

^a UNIVERSITY COLLEGE CORK   (Ireland)

Author keywords

competing commitments; groupthink; project management; resistance to change; virtual teams

Indexed keywords

EID: 85001575185     PISSN: 15483673     EISSN: 15483681     Source Type: Journal    
DOI: 10.4018/jec.2006070101     Document Type: Article

References (122)

1. Abrahamsson, P., & Iiavara, N. (2002). Commitment in software process improvement - In search of the process. Proceedings of the 35th Annual Hawaii International Conference on System Sciences (p. 206b). Washington, DC: IEEE Computer Press.
2. Abrahamsson, P., & Jokela, T. (2000). Development of management commitment to software process improvement. Proceedings of Information Systems Research 23 (pp. 487–505). Sweden: IRIS.
3. Agarwal, R., & Prasad, J. (2000). A field study of the adoption of software process innovations by information systems professionals. IEEE Transactions on Engineering Management, 47(3), 295–308.
4. Alsene, E. (1999). Internal changes and project management structures within enterprises. International Journal of Project Management, 17(6), 367–376.
5. Arrow, H., McGrath, J., & Berdahl, J. (2000). Small groups as complex systems. Thousand Oaks, CA: Sage Publications.
6. Asch, S. (1952). Social psychology. Upper Saddle River, NJ: Prentice-Hall.
7. Balthazard, P., Potter, R., & Warren, J. (2004a). Expertise, extraversion and group interaction styles as performance indicators in virtual teams. The Database for Advances in Information Systems, 35(1), 41–64.
8. Balthazard, P., Waldman, D., Howell, J., & Atwater, L. (2004b). Shared leadership and group interaction styles in problem-solving virtual teams. Proceedings of the 37th Hawaii International Conference on System Sciences (p. 10043a). Washington, DC: IEEE Computer Press.
9. Banerjee, R. (2003). Organisational character: Issues, imperatives and practices. International Journal of Human Resources Development and Management, 3(1), 72–83.
10. Baron, R., Kerr, N., & Miller, N. (1999). Group process, group decision, group action. Buckingham, UK: Open University Press.
11. Beck, K. (1999). Embracing change with extreme programming. IEEE Computer, 32(10), 70–77.
12. Beck, K. (2000). Extreme programming explained. Embrace change. Boston: Addison Wesley.
13. Beise, C. (2004). IT project management and virtual teams. Proceedings of the 2004 SIGMIS conference on computer personnel research (pp. 129–133). Tuscon, AZ: ACM Press.
14. Beynon-Davies, P. (1995). Information systems “failure”: The case of the London Ambulance Service's computer-aided despatch project. European Journal of Information Systems, I(3), 171–184.
15. Birmingham, D. (2002). Software development on a leash. New York: Springer-Verlag.
16. Boehm, B., & Egyed, A. (1998). Software requirements negotiation: Some lessons learned. Proceedings of the 20th international conference on Software Engineering (pp. 503–506). IEEE Computer Society.
17. Boehm, B., Egyed, A., Shah, A., Kwan, J., & Madachy, R. (1998). A stakeholder win-win approach to software education. Annals of Software Engineering, 6, 295–321.
18. Boehm, B., & Port, D. (2001). Balancing discipline and flexibility with the spiral model and MBASE. Crosstalk, 14(12).
19. Boody, D., Boonstra, A., & Kennedy, G. (2005). Managing information systems: An organisational perspective. Harlow, UK: Pearson Education.
20. Boody, D., & Macbeth, D. (2000). Prescriptions for managing change: A survey of their effects in projects to implement collaborative working between organizations. International Journal of Project Management, 18(5), 297–306.
21. Bowe, C., Lahey, L., Kegan, R., & Armstrong, E. (2003a). Questioning the big assumptions. Part I: Addressing personal contradictions that impede professional development. Medical Education, 37(8), 715–722.
22. Bowe, C., Lahey, L., Kegan, R., & Armstrong, E. (2003b). Questioning the big assumptions. Part II: Recognizing organizational contradictions that impede organisational change. Medical Education, 37(9), 723–733.
23. Burgess, R. (1982). Some role problems in field research. In R. Burgess (Ed.), Field research: A sourcebook and field manual (pp. 45–49). London: George Allen and Unwin Publishers.
24. Burnes, B. (2000). Managing change: A strategic approach to organisational dynamics. Harlow, UK: Pearson Education Ltd.
25. Cartwright, R. (2002). Mastering team leadership. Wales: Palgrave Macmillan.
26. Cascio, W., & Shurygailo, S. (2002). E-leadership and virtual teams. Organizational Dynamics, 31(4), 362–376.
27. Clarke, A. (1999). A practical use of key success factors to improve the effectiveness of project management. International Journal of Project Management, 17(3), 139–145.
28. Cohn, M., & Ford, D. (2003). Introducing an Agile process to an organisation. IEEE Computer, 36(6), 74–78.
29. Cushway, B., & Lodge, D. (1999). Organization behaviour and design. London: Kogan Page Ltd.
30. Duck, J. (1993). Managing change: The art of balancing. Harvard Business Review, 71(6), 109–118.
31. Erickson, T., Halveron, C., Kellog, W., Laff, M., & Wolf, T. (2002). Social translucence. Designing social infrastructures that make collective activity visible. Communications of the ACM, 45(4), 40–44.
32. Ezey, P. (2003). Integration and its challenges in participant observation. Qualitative Research, 3(2), 191–205.
33. Festinger, L., & Carlsmith, J. (2001). Cognitive consequences of forced compliance. In E. Coats & R. Feldman (Eds.) Classic and contemporary readings in social psychology (3rd ed.) (pp. 194–203). Upper Saddle River, NJ: Pearson Education. (Paper originally published in 1959)
34. Fetterman, D. (1991). A walk through the wilderness: Learning to find your way. In W. Shaffir & R. Stebbins (Eds.), Experiencing fieldwork: An inside view of qualitative research (pp. 87–96). Thousand Oaks, CA: Sage Publications.
35. Fichman, R., & Kemerer, C. (1999). The illusory diffusion of innovation: An examination of assimilation gaps. Information Systems Research, 10(3), 255–275.
36. Field, M., & Keller, L. (1998). Project management. London: Thomson Learning.
37. Fitzgerald, B. (1997). The use of systems development methodologies in practice: A field study. Information Systems Journal, 7(3), 210–212.
38. Fowler, M. (2000). Put your process on a diet. Software Development, 8(2), 32–36.
39. Fowler, M., & Highsmith, J. (2001). The Agile manifesto. Software Development, 9(8), 28–32.
40. Furst, S., Blackburn, R., & Rosen, B. (1999) Virtual team effectiveness: A proposed research agenda. Information Systems Journal, 9(4), 249–269.
41. Gallivan, M. (2001). Organizational adoption and assimilation of complex technological innovations: Development and application of a new framework. The Database for Advances in Information Systems, 32(3), 51–85.
42. Gallivan, M. (2004). Examining IT professionals' adaptation to technological change: The influence of gender and personal attributes. The Database for Advances in Information Systems, 35(3), 28–49.
43. Gephart, R. (1988). Status degradation and organizational succession. In J. Van Maanen (Ed.), Qualitative studies of organizations (pp. 159–191). Thousand Oaks, CA: Sage Publications.
44. Green, G., Collins, R., & Hevner, A. (2004). Perceived control and diffusion of software process innovations. Journal of High Technology Management, 15(1), 123–144.
45. Griffin, E. (1997). A first look at communication theory. New York: McGraw-Hill.
46. Gurney, J. (1991). Female research In male-dominated settings: Implications for short-term vs. long-term research. In W. Shaffir & R. Stebbins (Eds.), Experiencing fieldwork: An inside view of qualitative research (pp. 53–61). Thousand Oaks, CA: Sage Publications.
47. Harmon-Jones, E. (2001). Towards an understanding of the motivation underlying dissonance effects: Is the production of adverse consequences necessary? In E. Coats & R. Feldman (Eds.) Classic and contemporary readings in social psychology (3rd ed.) (pp. 204–213). NJ: Pearson Education. (Paper originally published in 1998)
48. Hartley, J. (1984). Case studies In organizational research. In C. Cassell & G. Symon (Eds.), Qualitative methods in organizational research (pp. 208–299). London: Sage Publications.
49. Huczynski, A., & Buchanan, D. (1991). Organizational behaviour. An introductory text (2nd ed.). New York: Prentice Hall.
50. Humphrey, S. (1989). Managing the software process. New York: Addison-Wesley.
51. Hunt, A., & Thomas, D. (2000). The pragmatic programmer. Boston: Addison Wesley Longman.
52. Hurwitz, J., Zander, A., & Hymovitch, B. (1968). Some effects of power on the relations among group members. In D. Cartwright & A. Zander (Eds.), Group dynamics (pp. 291–297). New York: Harper & Row Publishers.
53. Janis, I. (1972). Victims of groupthink. Boston: Houghton Mifflin Company.
54. Johnson, S., Suriya, C., Yoon, S., Ber-rett, J., & LaFleur, J. (2002). Team development and group processes of virtual learning teams. Computers & Education, 39, 379–393.
55. Jones, E., Gergen, K., Gumpert, P., & Thibaut, J. (1968). Some conditions affecting the use of ingratiation to influence performance evaluation. In D. Cartwright & A. Zander (Eds.), Group dynamics (pp. 278–289). New York: Harper & Row Publishers.
56. Jones, P., & Roelofsma, P. (2000). The potential for social contextual and group biases in team decision making: Biases, conditions, and psychological mechanisms. Ergonomics, 43(8), 1129–1152.
57. Jorgensen, D. (1989). Participant observation: A methodology for human studies. Thousand Oaks, CA: Sage Publications.
58. Kalita, T. (2003). DSDM in process improvement. In J. Stapleton (Ed.), DSDM business focused development (2nd ed.) (pp. 175–191). London: Pearson Education.
59. Kegan, R., & Lahey, L. (2001a). How the way we talk can change the way we work. CA: Jossey-Bass.
60. Kegan, R., & Lahey, L. (2001b). The real reason people won't change. Harvard Business Review, 79(10), 85–89.
61. Keil, M., Mann, J., & Rai, A. (2000). Why software projects escalate: An empirical analysis and test of four theoretical models. MIS Quarterly, 24(4), 631–660.
62. Kim, Y. (2001). A comparative study of the “Abilene paradox” and “groupthink.” Public Administration Quarterly, 25(2), 168–187.
63. Kohl, W. (1975). The Nixon-Kissinger foreign policy system and US-European relations: Patterns of policy making. World Politics, 28(1), 1–43.
64. Labaree, R. (2002). The risk of “going observationalist”: negotiating the hidden dilemmas of being an insider participant observer. Qualitative Research, 2(1), 97–122.
65. Lafleur, R. (1996). Project management. Getting control and keeping control of complex projects. American Programmer, 9(4), 24–28.
66. Lawrence, B. (1996). Unresolved ambiguity: The silent source of risk in your project. American Programmer, 9(4), 18–22.
67. Lee, J., & Truex, D. (2000). Exploring the impact of formal training in ISD methods on the cognitive structure of novice information systems developers. Information Systems Journal, 10(4), 347–367.
68. Lindvall, M., Basili, V., Boehm, B., Costa, P., Dangle, K., Shull, F., Tesoriero, R., Williams, L., & Zelkowitz, M. (2002). Empirical findings in agile methods. Extreme Programming and Agile methods - XP/Agile Universe Chicago 2002 (pp. 197–207). Sprin-ger-Verlag.
69. Lippit, R., Polansky, N., Redl, D., & Rosen, S. (1968). The dynamics of power. In D. Cartwright & A. Zander (Eds.), Group dynamics (pp. 236–250). NY: Harper & Row Publishers.
70. Lundell, B., & Lings, B. (2004). Changing perceptions of CASE technology. The Journal of Systems and Software, 72(2), 271–280.
71. Lurey, J., & Raisinghani, M. (2001). An empirical study of best practices in virtual teams. Information & Management, 38(8), 523–544.
72. Maoz, Z. (1990). Framing the national interest: The manipulation of foreign policy decisions in group settings. World Politics, 43(1), 77–110.
73. Martin, A., Biddle, R., & Noble, J. (2004). When XP met outsourcing. In J. Eckstein & H. Baumeister (Eds.), Extreme programming and Agile processes in software engineering. 5th International Conference (pp. 51–59). Germany: Springer-Verlag.
74. Martin, R. (1991). Working in groups. In M. Smith (Ed.), Analysing organisational behaviour (pp. 154–177). London: Macmillan Press.
75. Maskell, B. (2001). The age of agile manufacturing. Supply Change Management, 6(1), 5–11.
76. Maurer, F. (2002). Supporting distributed extreme programming. Extreme Programming and agile methods - XP/ Agile Universe (pp. 13–22). Chicago: Springer-Verlag.
77. McConnell, S. (2001). Managing outsourced projects: Project management inside out. In L. Constantine (Ed.), Beyond chaos: The expert edge in managing software development (pp. 103–110). NJ: Addison-Wesley.
78. McElroy, W. (1996). Implementing strategic change through projects. International Journal of Project Management, 14(6), 325–329.
79. Metzger, P. (1981). Managing a programming project. New York: Prentice Hall Inc.
80. Milgram, S. (1971). Group pressure and action against a person. In D. Taylor (Ed.), Small groups (pp. 157–170). Chicago: Markham Publishing Company.
81. Moorhead, G., Neck, C., & West, M. (1991). The tendency towards defective decision making with self-managing teams: The relevance of groupthink. Organizational Behaviour & Human Decision Process, 73(2), 327–351.
82. Mustonen-Ollila, & Lyytinen, K. (2003). Why organizations adopt information system process innovations: A longitudinal study using diffusion of innovation theory. Information Systems Journal, 13(3), 275–297.
83. Nader, D. (1993). Concepts for the management of organisational change. In C. Mabey & B. Major-White (Eds.), Managing change (2nd ed.) (pp. 5–19). London: Paul Chapman Publishing.
84. Nandhakumar, J., & Jones, M. (2002). Development gain? Participant observation in interpretive management information systems research. Qualitative Research, 2(3), 323–341.
85. Nash, D. (2002). Beyond buy-in. P&T Journal, 27(11), 617–618.
86. Neck, C. (1996). Letterman or Leno: A groupthink analysis of successive decisions made by the National Broadcasting Company. Journal of Managerial Psychology, 11(8), 3–17.
87. Newman, M., & Sabherwal, R. (1996). Determinants of commitment to information systems development: A longitudinal investigation. MIS Quarterly, 20(1), 23–54.
88. Orlikowski, W. (1993). CASE tools as organizational change: Investigating incremental and radical changes in systems development. MIS Quarterly, 17(3), 309–340.
89. Paul, S., Seetharamann, P., Samarah, I., & Mykytyn, P. (2004). Impact of heterogeneity and collaborative conflict management style on the performance of synchronous global virtual teams. Information & Management, 41(3), 303–321.
90. Pellegrinelli, S. (1997). Programme management: Organising project-based change. International Journal of Project Management, 15(3), 141–149.
91. Piccoli, G., & Ives, B. (2000). Virtual teams: Managerial behaviour control's impact on team effectiveness. Proceedings of the 21st International Conference on Information Systems (pp. 575–580). Atlanta, GA: AIS.
92. Potter, R., & Balthazard, P. (2002). Virtual team interaction styles: Assessment and effects. International Journal of Human-Computer Studies, 56(4), 423–443.
93. Powell, A., Picolli, G., & Ives, B. (2004). Virtual teams: A review of current literature and directions for future research. The Database for Advances in Information Systems, 35(1), 6–36
94. Rainwater, J. (2002). Herding cats: A primer for programmers who lead programmers. New York: Springer-Verlag.
95. Reeves, M., & Zhu, J. (2004). Moomba - A collaborative environment for supporting distributed extreme programming In global software development. In J. Eckstein & H. Baumeister (Eds.), Extreme programming and agile processes in software engineering. 5th International Conference (pp. 38–50). Heidelberg,Germany: Springer-Verlag.
96. Reichheld, F. (2001). Lead for loyalty. Harvard Business Review, 79(7), 76–84.
97. Robbins, H., & Finley, M. (1998) Why change doesn't work. London: Orion Publishing.
98. Robinson, H., & Sharp, H. (2004). The characteristics of XP teams. In J. Eckstein & H. Baumeister (Eds.), Extreme programming and agile processes in software engineering. 5th International Conference (pp. 139–147). Heidelberg, Germany: Springer-Verlag.
99. Rogers, E. (1962). Diffusion of innovations. New York: The Free Press.
100. Schelling, T. (1989). The mind as a consuming organ. In D. Bell, H. Raiffa, & A. Tversty (Eds.), Decision making. Descriptve, normative, and prescriptive interactions (pp. 343–357). Cambridge, UK: Cambridge University Press.
101. Schwaber, K. (1996). Controlled chaos. Living on the edge. American Programmer, 9(4), 11–16.
102. Schwartzman, H. (1993). Ethnography in organizations. Thousand Oaks,CA: Sage Publications.
103. Sepulveda, C. (2003). Agile development and remote teams: Learning to love the phone. Proceedings of the Agile Development Conference (pp. 140–145). Washington, DC: IEEE Computer Society.
104. Siegel, A., & Siegel, S. (1968). Reference groups, membership groups, and attitude change. In D. Cartwright, & A. Zander (Eds.), Group dynamics (pp. 74–79). New York: Harper & Row Publishers.
105. Sparks, D. (2002). Inner conflicts, inner strengths. Journal of Staff Development, 23(3), 66–71.
106. Spradley, J. (1980). Participant observation. New York: Holt, Rinehard, and Winston.
107. Stotts, D., Williams, L., Nagappan, N., Baheti, P., Jen, D., & Jackson. A. (2003). Virtual teaming: Experiments and experiences with distributed pair programming. In F. Maurer, & D. Wells (Eds.), Extreme programming and Agile methods - Xp/Agile universe 2003 (pp. 129–141). New Orleans, LA: Springer-Verlag.
108. Sunstrom, E., DeMeuse, K., & Futrell, D. (1990). Work teams: Applications and effectiveness. American Psychologist, 45(2), 120–133.
109. Tavares-Rixon, D. (2003). Exploring the nature of commitment to software quality initiatives: A political perspective. Proceedings of the First Australian Undergraduate Students Computing Conference (pp. 87–92). Melbourne: AUSCC.
110. Tedlock, B. (2000). Ethnography and ethnographic presentation. In N. Denzin, & Y. Lincoln (Eds.), Handbook of qualitative research (2nd ed.) (pp. 455–486). Thousand Oaks, CA: Sage Publications.
111. Thomsett, R. (1998). The care and feeding of project managers. American Programmer, 11(2), 5–11.
112. Toleman, M., Ally, M., & Darroch, F. (2004). Aligning adoption theory with agile system development methodologies. Proceedings of the 8th Pacific Asia Conference on Information Systems (pp. 458–471). Shanghai: AIS.
113. Traylen, H. (1994). Confronting hidden agendas: Cooperative inquiry with health visitors. In P. Reason (Ed.), Participation in human inquiry (pp. 59–81). London: Sage Publications.
114. Turner, J., & Muller, R. (2003). On the nature of the project as a temporary organization. International Journal of Project Management, 21(1), 1–8.
115. Von Bergen, C., & Kirk, R. (1978). Group-think: When too many heads spoil the decision. Management Review, 67(3), 44–49.
116. Weinberg, G. (1971). The psychology of computer programming. New York: Van Nostrand Reinhold Co.
117. Whitehead, R. (2001). Leading a software development team. A developers guide to successfully leading people and projects. London: Addison-Wesley.
118. Wright, J., & Schaal, D. (1988). Group-think: The trap of consensus investing. Journal of Financial Planning, 1(1), 41–44.
119. Yourdon, E. (1993). Decline and fall of the American programmer. Upper Saddle River, NJ: Prentice Hall Inc.
120. Zachary, G. (1994). Show-stopper! The breakneck race to create Windows NT and the next generation at Microsoft. New York: The Free Press.
121. Zigurs, I., (2003). Leadership in virtual teams: Oxymoron or opportunity? Organizational Dynamics, 31(4), 339–351.
122. Zmud,R. (1983). The effectiveness of external information channels in facilitating innovation within software development groups. MIS Quarterly, 7(2), 43–58.