Using agile practices to build trust in an agile team: A case study

Information Systems Development - Business Systems and Services: Modeling and Development

Volumn , Issue , 2011, Pages 503-516

  McHugh, Orla ^a   Conboy, Kieran ^b   Lang, Michael ^b  

^a NATIONAL UNIVERSITY OF IRELAND   (Ireland)

^b NONE

Author keywords

[No Author keywords available]

Indexed keywords

AGILE CONTEXTS; AGILE PRACTICES; ENVIRONMENTAL CONDITIONS; EXPLORATORY CASE STUDIES; ITERATION PLANNING; PERSONAL CHARACTERISTICS; SELF-MANAGING TEAM; SOFTWARE DEVELOPMENT TEAMS;

MANAGEMENT INFORMATION SYSTEMS; SOFTWARE DESIGN;

INFORMATION SYSTEMS;

EID: 84865527763     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1007/978-1-4419-9790-6_40     Document Type: Conference Paper

References (39)

1. Abrahamsson P, Conboy K, Wang X (2009) Lots done, more to do: The current state of agile systems development research. Eur J Inf Syst 18(4):281-284.
2. Agile Alliance (2001) Manifesto for agile software development. www.agilemanifesto.org.
3. Alper S, Tjosvold D, Law KS (1998) Interdependence and controversy in group decision making: Antecedents to effective self-managing teams. Organ Behav Hum Dec Process 74(1):33-52.
4. Barker JR (1993) Tightening the iron cage: concertive control in self-managing teams. Admin Sci Q 38(3):408-437.
5. Beck K, Andres C (2005) Extreme programming explained: embrace change, 2nd edn. Addison- Wesley, Boston.
6. Benbasat I, Goldstein DK, Mead M (1987) The case research strategy in studies of information systems. MIS Q 11(3):368-386.
7. Bishop JW, Scott KD, Burroughs SM (2000) Support, commitment, and employee outcomes in a team environment. J Manage 26(6):1113-1132.
8. Blomqvist K (1997) The many faces of trust. Scand J Manage 13(3):271-286.
9. Boehm B (2002) Get ready for agile methods, with care. IEEE Comput 35(1):64-69.
10. Cockburn A, Highsmith J (2001) Agile software development: The people factor. IEEE Comput 34(11):131-133.
11. Cohen SG, Chang LEI, Ledford GEJ (1997)Ahierarchical construct of self-management leadership and its relationship to quality of work life and perceived work group effectiveness. Person Psychol 50(2):275-308.
12. Conboy K (2009) Agility from first principles: reconstructing the concept of agility in information systems development. Inf Syst Res 20(3):329-354.
13. Cooper DR, Schindler PS (2001) Business research methods. 8th edn. McGraw-Hill, London.
14. Cummings TG (1978) Self-regulating work groups: A socio-Technical synthesis. Acad Manage Rev 3(3):625-634.
15. Das TK, Teng B-S (2001) Trust, control, and risk in strategic alliances: An integrated framework. Organ Stud 22(2):251-283.
16. Dybå, T, Dingsøyr T (2008) Empirical studies of agile software development: A systematic review. Inf Softw Technol 50(9-10):833-859.
17. Elssamadisy A (2007) Patterns of agile practice adoption: The technical cluster. C4Media, Santa Ana.
18. Elssamadisy A (2008) Agile adoption patterns: A roadmap to organizational success. Addisson Wesley, Upper Saddle River.
19. Gruenfeld DH, Mannix EA, Williams KY, Neale MA (1996) Group composition and decision making: how member familiarity and information distribution affect process and performance. Organ Behav Hum Dec Process 67:1-15.
20. Hackman JR (1990) Groups that work (and those that don't). Creating conditions for effective teamwork. Jossey-Bass, San Francisco.
21. Hansson C, DittrichY, Gustafsson B, Zarnak S (2006)Howagile are industrial software development practices? J Syst Softw 79(9):1295-1311.
22. Hofstede G (1980) Motivation, leadership, and organization: do American theories apply abroad? Organ Dyn Summer:42-63.
23. Jurison J (1999) Software project management: The manager's view. Commun AIS 2(17):1-50.
24. Kramer RM (1999) Trust and distrust in organizations: emerging perspectives, enduring questions. Annu J Psychol 50(1):569-598.
25. Lewicki RJ, McAllister DJ, Bies RJ (1998) Trust and distrust: new relationships and realities. Acad Manage Rev 23(3):438-458.
26. Manz CC, Sims HP Jr (1987) Leading workers to lead themselves: The external leadership of self-managing work teams. Admin Sci Q 32(1):106-129.
27. Maruping LM, Venkatesh V, Agarwal R (2009) A control theory perspective on agile methodology use and changing user requirements. Inf Syst Res 20(3):377-399. doi:10.1287/isre.1090.0238.
28. Mayer RC, Davis JH, Schoorman FD (1995) An integrative model of organizational trust. Acad Manage Rev 20(3):709-734.
29. McEvoy J, Butler T (2009) The role of project management in ineffective decision making within Agile software development projects. Eur J Inf Syst 18(4):372-383.
30. McKnight DH, Cummings TG, Chervany NL (1998) Initial trust formation in new organizational relationships. Acad Manage Rev 23(3):473-490.
31. Miles M, Huberman A (1999) Qualitative data analysis. Sage, London.
32. Moe NB, Dingsøyr T, Dybå T (2010) A teamwork model for understanding an agile team: A case study of a Scrum project. Inf Softw Technol 52(5):480-491.
33. Nerur S, Mahapatra R, Mangalara G (2005) Challenges of migrating to agile methodologies. Commun ACM 48(5):72-78.
34. Ramesh B, Cao L, Mohan K (2006) Can distributed software development be agile? CommunACM 49(10):41-46.
35. Rousseau DM, Sitkin SB, Burt RS, Camerer C (1998) Not so different after all: A cross-discipline view of trust. Acad Manage Rev 23(3):393-404.
36. Schwaber K, Beedle M(2002) Agile software development with Scrum. Prentice-Hall, Englewood Cliffs.
37. Version One (2009) State of agile development survey 2009. http://pm.versionone.com/StateofAgileSurvey.html. Accessed 31 Mar 2010.
38. Wageman R (1997) Critical success factors for creating superb self-managing teams. Organ Dyn 26(1):49-61.
39. Wageman R, Fisher CM, Hackman JR (2009) Leading teams when the time is right: finding the best moments to act. Organ Dyn 38(3):192-203.