This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Agile Practices: The Impact on Trust in Software Project Teams
May-June 2012 (vol. 29 no. 3)
pp. 71-76
Orla McHugh, National University of Ireland Galway
Kieran Conboy, Australian School of Business, Sydney
Michael Lang, National University of Ireland Galway
Agile software development involves self-managing teams that are empowered and responsible for meeting project goals in whatever way they deem suitable. Managers must place more trust in such teams than they do in teams following more traditional development methodologies. The authors highlight how the use of agile practices can enhance trust amongst agile team members. They also present challenges that agile teams can face as a result of using agile practices. Their results are based on the findings from three case studies of agile software development teams.

1. AgileAlliance, “Manifesto for Agile Software Development,” 2001; www.agilemanifesto.org.
2. S. Nerur, R. Mahapatra, and G. Mangalara, “Challenges of Migrating to Agile Methodologies,” Comm. ACM, vol. 48, no. 5, 2005, pp. 72–78.
3. E. Hasnain and T. Hall, “Investigating the Role of Trust in Agile Methods Using a Light Weight Systematic Literature Review,” Agile Processes in Software Engineering and Extreme Programming, Springer, 2008, pp. 204–207.
4. R.C. Mayer, J.H. Davis, and F.D. Schoorman, “An Integrative Model of Organizational Trust,” Academy of Management Rev., vol. 20, no. 3, 1995, pp. 709–734.
5. T.K. Das and B.-S. Teng, “Trust, Control, and Risk in Strategic Alliances: An Integrated Framework,” Organization Studies, vol. 22, no. 2, 2001, pp. 251–283.
6. J. Iivari and N. Iivari, “The Relationship between Organizational Culture and the Deployment of Agile Methods,” Information and Software Technology, vol. 53, no. 5, 2011, pp. 509–520.
7. B. Ramesh, L. Cao, and K. Mohan, “Can Distributed Software Development Be Agile?” Comm. ACM, vol. 49, no. 10, 2006, pp. 41–46.
8. G. Piccoli and B. Ives, “Trust and the Unintended Effects of Behavior Control in Virtual Teams,” MIS Q., vol. 27, no. 3, Sept. 2003, pp. 365–395.
9. “State of Agile Development Survey 2009,” white paper, VersionOne, 2009; http://pm.versionone.comStateofAgileSurvey.html .
10. O. McHugh,K. Conboy, and M. Lang, “Using Agile Practices to Build Trust in an Agile Team: A Case Study,” Proc. 19th Int'l Conf. Information Systems Development, Springer, 2010, pp. 503–516.
11. J. Chong, “Social Behaviors on XP and Non-XP teams: A Comparative Study,” Proc. Agile Development Conf., IEEE CS, 2005, pp. 39–48.
12. H. Sharp and H. Robinson, “Collaboration and Co-ordination in Mature eXtreme Programming Teams,” Int'l J. Human-Computer Studies, vol. 66, no. 7, 2008, pp. 506–518.
13. E. Whitworth and R. Biddle, “Motivation and Cohesion in Agile Teams,” Proc. 8th Int'l Conf. (XP 2007), Springer, 2007, pp. 62–69.

Index Terms:
agile methodology, agile practice, daily stand-up, planning, retrospective, trust, culture, distributed software engineering
Citation:
Orla McHugh, Kieran Conboy, Michael Lang, "Agile Practices: The Impact on Trust in Software Project Teams," IEEE Software, vol. 29, no. 3, pp. 71-76, May-June 2012, doi:10.1109/MS.2011.118
Usage of this product signifies your acceptance of the Terms of Use.