Understanding lack of trust in distributed agile teams: A grounded theory study

IET Seminar Digest

Volumn 2012, Issue 1, 2012, Pages 81-90

  Dorairaj, Siva ^a   Noble, James ^a   Malik, Petra ^a  

^a VICTORIA UNIVERSITY OF WELLINGTON   (New Zealand)

Author keywords

[No Author keywords available]

Indexed keywords

ADVERSE EFFECT; AGILE TEAMS; AUSTRALIA; DISTRIBUTED SOFTWARE DEVELOPMENT; DISTRIBUTED TEAMS; GROUNDED THEORY; SELF ORGANIZING; SOFTWARE COMPANY; SOFTWARE DEVELOPMENT TEAMS; TEAM PERFORMANCE; THEORETICAL MODELS;

SOFTWARE DESIGN;

DISTRIBUTED COMPUTER SYSTEMS;

EID: 84865487991     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1049/ic.2012.0011     Document Type: Conference Paper

References (73)

1. N. Abbas, A. M. Gravell, and G. B. Wills. Historical roots of Agile methods: Where did Agile thinking come from? In Agile Processes in Software Engineering and Extreme Programming, volume 9 of Lecture Notes in Business Information Processing, pages 94-103. Springer Berlin Heidelberg, 2008.
2. S. Adolph,W. Hall, and P. Kruchten. A methodological leg to stand on: Lessons learned using grounded theory to study software development. In Proceedings of the 2008 Conference of the Center for Advanced Studies on Collaborative Research, pages 166-178, New York, NY, USA, 2008. ACM.
3. G. Allan. A critique of using grounded theory as a research method. Electronic Journal of Business Research Methods, 2:1-10, 2003.
4. M. J. Angen. Evaluating interpretive inquiry: Reviewing the validity debate and opening the dialogue. Qualitative Health Research, 10(3):378-395, 2000.
5. G. Asproni. Motivation, teamwork, and Agile development. Agile Times, 4(1):8-15, 2004.
6. M. A. Babar, J. M. Verner, and P. T. Nguyen. Establishing and maintaining trust in software outsourcing relationships: An empirical investigation. Journal of Systems and Software, 80(9):1438-1449, 2007.
7. K. Beck. Extreme Programming Explained: Embrace Change. Addison-Wesley, Upper Saddle River, 2000.
8. I. Bose. Lessons learned from distributed Agile software projects: A case-based analysis. Communications of the Association for Information Systems, 23(1):619-632, 2008.
9. R. P. Bostrom. Successful application of communication techniques to improve the systems development process. Information & Management, 16(5):279-295, 1989.
10. E. Carmel. Thirteen assertions for globally dispersed software development research. In Proceedings of the Thirtieth Hawaii International Conference on System Sciences, volume 3, pages 445-452, 1997.
11. A. Cockburn. Agile Software Development. Addison-Wesley, Indianapolis, 2002.
12. A. Cockburn and J. Highsmith. Agile software development: The people factor. Computer, 34(11):131-133, 2001.
13. J. W. Creswell. Qualitative Inquiry and Research Design: Choosing Among Five Approaches. Sage Publications, Thousand Oaks, CA, USA, 1998.
14. A. Crossman and L. Lee-Kelley. Trust, commitment and team working: The paradox of virtual organizations. Global Networks, 4(4):375-390, 2004.
15. K. Crowston, J. Howison, C. Masango, and U. Y. Eseryel. The role of face-to-face meetings in technology-supported self-organizing distributed teams. Professional Communication, IEEE Transactions on, 50(3):185-203, Sept. 2007.
16. S. Dorairaj, J. Noble, and P. Malik. Understanding the importance of trust in distributed Agile projects: A practical perspective. In Agile Processes in Software Engineering and Extreme Programming, volume 48 of Lecture Notes in Business Information Processing, pages 172-177. Springer Berlin Heidelberg, Trondheim, Norway, 2010.
17. S. Dorairaj, J. Noble, and P. Malik. Bridging cultural differences: A grounded theory perspective. In Proceedings of the 4th India Software Engineering Conference, ISEC '11, pages 3-10, New York, NY, USA, 2011. ACM.
18. S. Dorairaj, J. Noble, and P. Malik. Effective communication in distributed Agile software development teams. In Agile Processes in Software Engineering and Extreme Programming, volume 77 of Lecture Notes in Business Information Processing, pages 102-116. Springer Berlin Heidelberg, 2011.
19. S. Dorairaj, J. Noble, and P. Malik. Distribution and Agility: It's all about trust. Technical Report ECSTR-12-01, Victoria University of Wellington, New Zealand, January 2012.
20. S. Dorairaj, J. Noble, and P. Malik. Understanding team dynamics in distributed Agile software development. Technical Report ECSTR-12-02, Victoria University of Wellington, New Zealand, January 2012.
21. T. Dybå and T. Dingsøyr. What do we know about Agile software development? IEEE Software, 26(5):6-9, Sept/Oct 2009.
22. C. M. Fiol and E. J. O'Connor. Identification in face-to-face, hybrid, and pure virtual teams: Untangling the contradictions. Organization Science, 16(1):19-32, 2005.
23. S. M. Fiore. Distributed coordination space: Toward a theory of distributed team process and performance. Theoretical Issues in Ergonomics Science, 4(3-4):340-364, 2003.
24. B. Fitzgerald, G. Hartnett, and K. Conboy. Customising Agile methods to software practices at Intel Shannon. European Journal of Information System, 15(2):200-213, 2006.
25. M. Fowler and J. Highsmith. The agile manifesto. Software Development, 9(8):28-35, 2001.
26. S. Georgieva and G. Allan. Best practices in project management through a grounded theory lens. Electronic Journal of Business Research Methods, 6(1):43-52, 2008.
27. B. Glaser. Theoretical Sensitivity: Advances in Methodology of Grounded Theory. Sociology Press, Mill Valley, CA, 1978.
28. B. Glaser. Basics of Grounded Theory Analysis: Emergence vs Forcing. Sociology Press, Mill Valley, CA, 1992.
29. B. Glaser. Doing Grounded Theory: Issues and Discussions. Sociology Press, Mill Valley, CA, 1998.
30. B. Glaser. The Grounded Theory Perspective III: Theoretical Coding. Sociology Press, Mill Valley, CA, 2005.
31. B. G. Glaser. The constant comparative method of qualitative analysis. Social Problems, 12(4):436-445, 1965.
32. B. G. Glaser and A. L. Strauss. The Discovery of Grounded Theory: Strategies for Qualitative Research. Sociology Press, Aldine, Chicago, 1967.
33. D. H. Gobeli, H. F. Koenig, and I. Bechinger. Managing conflict in software development teams: A multilevel analysis. Journal of Product Innovation Management, 15(5):423-435, 1998.
34. E. Hasnain and T. Hall. Investigating the role of trust in Agile methods using a light weight systematic literature review. In Agile Processes in Software Engineering and Extreme Programming, volume 9 of Lecture Notes in Business Information Processing, pages 204-207. Springer Berlin Heidelberg, 2008.
35. J. A. Highsmith, III. Adaptive Software Development: A Collaborative Approach to Managing Complex Systems. Dorset House Publishing, New York, USA, 2000.
36. R. Hoda, J. Noble, and S. Marshall. Developing a grounded theory to explain the practices of self-organizing Agile teams. Empirical Software Engineering, pages 1-31.
37. R. Hoda, J. Noble, and S. Marshall. Organizing self-organizing teams. In Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering, pages 285-294, New York, USA, 2010.
38. E. Hossain, M. A. Babar, and J. Verner. Towards a framework for using Agile approaches in global software development. In Product- Focused Software Process Improvement, volume 32 of Lecture Notes in Business Information Processing, pages 126-140. Springer Berlin Heidelberg, 2009.
39. S. L. Jarvenpaa, T. R. Shaw, and D. Staples. Toward contextualized theories of trust: The role of trust in global virtual teams. Information Systems Research, 15, 2004.
40. M. C. Jones and A. W. Harrison. Is project team performance: An empirical assessment. Information & Management, 31(2):57-65, 1996.
41. M. Korkala, M. Pikkarainen, and K. Conboy. Distributed Agile development: A case study of customer communication challenges. In Agile Processes in Software Engineering and Extreme Programming, volume 31 of Lecture Notes in Business Information Processing, pages 161-167. Springer Berlin Heidelberg, 2009.
42. M. C. Lander, R. L. Purvis, G. E. McCray, and W. Leigh. Trustbuilding mechanisms utilized in outsourced IS development projects: A case study. Information & Management, 41(4):509-528, 2004.
43. L. Layman, L. Williams, D. Damian, and H. Bures. Essential communication practices for Extreme Programming in a global software development team. Information and Software Technology, 48(9):781-794, 2006. Special Issue Section: Distributed Software Development.
44. K. Lomborg and M. Kirkevold. Truth and validity in grounded theory:a reconsidered realist interpretation of the criteria: Fit, work, relevance and modifiability. Nursing Philosophy, 4(3):189-200, 2003.
45. A. Martin, R. Biddle, and J. Noble. The XP customer team: A grounded theory. In Proceedings of the AGILE, pages 57-64, 2009.
46. O. McHugh, K. Conboy, and M. Lang. The impact of Agile practices on trust in software project teams. Software, IEEE, PP(99):1, 2011.
47. O. McHugh, K. Conboy, and M. Lang. Using Agile practices to build trust in an Agile team: A case study. In Information Systems Development, pages 503-516. Springer New York, 2011.
48. N. B. Moe, T. Dingsoyr, and T. Dyba. Understanding self-organizing teams in Agile software development. In ASWEC 2008, 19th Australian Conference on Software Engineering, pages 76-85, March 2008.
49. N. B. Moe and D. ? Smite. Understanding lacking trust in global software teams: A multi-case study. In J. Münch and P. Abrahamsson, editors, Product-Focused Software Process Improvement, volume 4589 of Lecture Notes in Computer Science, pages 20-34. Springer Berlin Heidelberg, 2007.
50. A. Moghaddam. Coding issues in grounded theory. Issues In Educational Research, 16:52-66, 2006.
51. S. Nerur, R. Mahapatra, and G. Mangalaraj. Challenges of migrating to Agile methodologies. Communications of ACM, 48:72-78, May 2005.
52. N. V. Oza, T. Hall, A. Rainer, and S. Grey. Trust in software outsourcing relationships: An empirical investigation of Indian software companies. Information and Software Technology, 48(5):345-354, 2006.
53. M. Paasivaara and C. Lassenius. Could global software development benefit from Agile methods? In Proceedings of the IEEE International Conference on Global Software Engineering, pages 109-113, Washington, DC, USA, 2006. IEEE Computer Society.
54. S. Palmer and M. Felsing. A Practical Guide to Feature-Driven Development. Pearson Education, 2001.
55. R. Prikladnicki, J. Audy, and R. Evaristo. Distributed software development: Toward an understanding of the relationship between project team, users and customers. In Proceedings of International Conference on Enterprise Information Systems, Angers, France, 2003.
56. B. Ramesh, L. Cao, K. Mohan, and P. Xu. Can distributed software development be Agile? Communication of the ACM, 49(10):41-46, 2006.
57. H. Robinson and H. Sharp. The characteristics of XP teams. In J. Eckstein and H. Baumeister, editors, Extreme Programming and Agile Processes in Software Engineering, volume 3092 of Lecture Notes in Computer Science, pages 139-147. Springer Berlin / Heidelberg, 2004.
58. R. Sabherwal. The role of trust in outsourced IS development projects. Communications of ACM, 42:80-86, February 1999.
59. M. Sandelowski. Rigor or rigor mortis: The problem of rigor in qualitative research revisited. Advances in Nursing Science, 16(2):1-8, Dec. 1993.
60. R. S. Schreiber and P. N. Stern. Using Grounded Theory in Nursing. Springer Publishing, Broadway, New York, 2001.
61. K. Schwaber and M. Beedle. Agile Software Development with Scrum. Prentice Hall PTR, Upper Saddle River, NJ, USA, 2001.
62. L. Seiyoung and Y. Hwan-Seung. Distributed Agile: Project management in a global environment. Empirical Software Engineering, 15(2):204-217, 2010.
63. H. Sharp and H. Robinson. Collaboration and coordination in mature eXtreme programming teams. International Journal of Human- Computer Studies, 66(7):506-518, 2008. Collaborative and Social Aspects of Software Development.
64. D. Silverman. Qualitative research: Meanings or practices? Information Systems Journal, 8(1):3-20, 1998.
65. J. K. Smith. The problem of criteria for judging interpretive inquiry. Educational Evaluation and Policy Analysis, 6(4):379-391, 1984.
66. K. K. Smith and D. N. Berg. A paradoxical conception of group dynamics. Human Relations, 40(10):633-657, October 1987.
67. J. Stapleton. Dynamic Systems Development Method: The Method in Practice. Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA, 1997.
68. A. Strauss and J. Corbin. Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory. Sage Publications, 1998.
69. S. D. Teasley, L. A. Covi, M. Krishnan, and J. S. Olson. Rapid software development through team collocation. Software Engineering, IEEE Transactions on, 28(7):671-683, July 2002.
70. C. Urquhart, H. Lehmann, and M. D. Myers. Putting the 'theory' back into grounded theory: guidelines for grounded theory studies in information systems. Information Systems, 20(4):357-381, 2010.
71. R. Whittemore, S. K. Chase, and C. L. Mandle. Validity in qualitative research. Qualitative Health Research, 11(4):522-537, 2001.
72. E. Whitworth and R. Biddle. The social nature of Agile teams. In Proceedings of the AGILE, pages 26-36, Washington, DC, USA, 2007. IEEE Computer Society.
73. J. Winkler, J. Dibbern, and A. Heinzl. The impact of cultural differences in offshore outsourcing:case study results from German-Indian application development projects. Information Systems Frontiers, 10:243-258, 2008.