Using agile practices to influence motivation within IT project teams

Scandinavian Journal of Information Systems

Volumn 23, Issue 2, 2011, Pages 59-84

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

^a University of Limerick   (Ireland)

^b UNIVERSITY OF NEW SOUTH WALES   (Australia)

Author keywords

Agile project management; Information systems; Information technology; Motivation; Scrum

Indexed keywords

EID: 84869189369     PISSN: 09050167     EISSN: 19010990     Source Type: Journal    
DOI: None     Document Type: Article

References (62)

1. Abrahamsson, P., Conboy, K., and Wang, X., (2009). Lots done, more to do: The current state of agile systems development research. European Journal of Information Systems, (18:4): 281-284.
2. Abrahamsson, P., Salo, O., Ronkainen, J., and Warsta, J. (2002). Agile software development methods: Review and Analysis. Espoo, Finland: Technical Research Centre of Finland, VTT Publications 478.
3. AgileAlliance. (2001). "Manifesto for Agile Software Development". Accessed January 14th, 2010 at www.agilemanifesto.org.
4. Alper, S., Tjosvold, D., and Law, K. S., (1998). Interdependence and Controversy in Group Decision Making: Antecedents to Effective Self-Managing Teams. Organizational Behavior and Human Decision Processes, (74:1): 33-52.
5. Asproni, G. (2004). Motivation, Teamwork and Agile Development, Agile Times (Vol. 4).
6. Barker, J. R., (1993). Tightening the Iron Cage: Concertive Control in Self-Managing Teams. Administrative Science Quarterly, (38:3): 408-437.
7. Beck, K., and Andres, C., (2005). Extreme Programming Explained: Embrace Change, (2nd ed. ed.), Addison-Wesley, Boston, MA.
8. Beecham, S., Baddo, N., Hall, T., Robinson, H., and Sharp, H., (2008). Motivation in Software Engineering: A Systematic Literature Review. Information and Software Technology, (50:9-10): 860-878.
9. Bishop, J. W., Scott, K. D., and Burroughs, S. M., (2000). Support, commitment, and employee outcomes in a team environment. Journal of Management, (26:6): 1113-1132.
10. Boehm, B., (1981). Software Engineering Economics, Prentice Hall.
11. Boehm, B., (1988). A spiral model of software development and maintenance. IEEE Computer, (21:5): 61-72.
12. Boehm, B., (2002). Get Ready for Agile Methods, With Care. IEEE Computer, (35:1): 64-69.
13. Boehm, B., and Turner, R., (2005). Management Challenges to Implementing Agile Processes in Traditional Development Organizations. IEEE Software, (22:5): 30-39.
14. Cockburn, A., and Highsmith, J., (2001). Agile Software Development: The People Factor. IEEE Computer, (34:11): 131-133.
15. Cohen, S. G., and Bailey, D. E., (1997). What makes teams work: Group effectiveness research from the shop floor to the executive suite. Journal of Management, (23:3): 239-290.
16. Cohen, S. G., Chang, L. E. I., and Ledford, G. E. J., (1997). A Hierarchical Construct of Self-Management Leadership and its Relationship to Quality of Work Life and Perceived Work Group Effectiveness. Personnel Psychology, (50:2): 275-308.
17. Cohn, M., and Ford, D., (2003). Introducing an agile process to an organization IEEE Computer, (36:6): 74-78.
18. Conboy, K., (2009). Agility from first principles: Reconstructing the concept of agility in information systems development. Information Systems Research, (20:3): 329-354.
19. Conboy, K., Coyle, S., Xiaofeng, W., and Pikkarainen, M., (2011). People over Process: Key Challenges in Agile Development. IEEE Software, (28:4): 48-57.
20. Coram, M., and Bohner, S., The Impact of Agile Methods on Software Project Management, Engineering of Computer-Based Systems, 2005. ECBS '05. 12th IEEE International Conference and Workshops on the, 2005, pp. 363-370.
21. Cummings, T. G., (1978). Self-Regulating Work Groups: A Socio-Technical Synthesis. The Academy of Management Review, (3:3): 625-634.
22. Das, T. K., and Teng, B.-S., (2001). Trust, Control, and Risk in Strategic Alliances: An Integrated Framework. Organization Studies, (22:2): 251-283.
23. DeMarco, T., and Lister, T., (1987). Peopleware: Productive Projects and Teams, Dorset House Publishing Co., NY.
24. Dybå, T., and Dingsøyr, T., (2008). Empirical Studies of Agile Software Development: A Systematic Review. Information and Software Technology, (50:9-10): 833-859.
25. Eisenhardt, K. M., (1989). Building Theories from Case Study Research. The Academy of Management Review, (14:4): 532-550.
26. Elssamadisy, A., (2007). Patterns of Agile Practice Adoption: The Technical Cluster, C4Media, USA.
27. Elssamadisy, A., (2008). Agile Adoption Patterns: A Roadmap to Organizational Success, Addisson Wesley, USA.
28. Fitzgerald, B., Hartnett, G., and Conboy, K., (2006). Customising Agile Methods to Software Practices at Intel Shannon. European Journal of Information Systems, (15:2): 197-210.
29. Gruenfeld, D. H., Mannix, E. A., Williams, K. Y., and Neale, M. A., (1996). Group Composition and Decision Making: How Member Familiarity and Information Distribution Affect Process and Performance. Organizational Behavior and Human Decision Processes, (67:1): 1-15.
30. Hackman, J. R., (1990). Groups that Work (and those that don't). Creating Conditions for Effective Teamwork, Jossey-Bass Inc. San Francisco, CA.
31. Hall, T., Sharp, H., Beecham, S., Baddo, N., and Robinson, H., (2008). What do we know about Developer Motivation? IEEE Software, (25:4): 92-94.
32. Hansson, C., Dittrich, Y., Gustafsson, B., and Zarnak, S., (2006). How Agile are Industrial Software Development Practices? Journal of Systems and Software, (79:9): 1295-1311.
33. Herzberg, F., (1968). One more time: How do you motivate employees? Harvard Business Review, (46:1): 53-62.
34. Jurison, J., (1999). Software Project Management: The Manager's View. Communications of the AIS, (2:17): 1-50.
35. Locke, E. A., (1968). Toward a theory of task motivation and incentives. Organizational Behavior and Human Performance, (3:2): 157-189.
36. Manz, C. C., and Sims, H. P., Jr., (1987). Leading Workers to Lead Themselves: The External Leadership of Self-Managing Work Teams. Administrative Science Quarterly, (32:1): 106-129.
37. Maruping, L. M., Venkatesh, V., and Agarwal, R., (2009). A Control Theory Perspective on Agile Methodology Use and Changing User Requirements. Information Systems Research, (20:3): 377-399.
38. Mayer, R. C., Davis, J. H., and Schoorman, F. D., (1995). An Integrative Model of Organizational Trust. Academy of Management Review, (20:3): 709-734.
39. Mayo, E., (1949). The social problems of an industrial civilization, London, England, Routledge & K. Paul.
40. McEvoy, J., and Butler, T., (2009). The role of project management in ineffective decision making within Agile software development projects. European Journal of Information Systems, (18:4): 372-383.
41. Miles, M., and Huberman, A., (1999). Qualitative Data Analysis, London, Sage.
42. Moe, N. B., Dingsøyr, T., and Dybå, T., (2010). A teamwork model for understanding an agile team: A case study of a Scrum project. Information and Software Technology, (52:5): 480-491.
43. Nerur, S., Mahapatra, R., and Mangalara, G., (2005). Challenges of Migrating to Agile Methodologies. Communications of the ACM, (48:5): 72-78.
44. Parnas, D., (2006). Agile Methods and GSD: The wrong solution to an old but real problem. Communications of the ACM, (49:10): 29-29.
45. Patton, M., (1990). Qualitative Evaluation and Research Methods, Newbury Park, CA, Sage.
46. Pettigrew, A. M., (1990). Longitundinal Research on Change: Theory and Practice. Organization Science, (1:3): 267-292.
47. Rising, L., and Janoff, N., (2000). The Scrum Software Development Process for Small Teams. IEEE Software, (17:4): 26-32.
48. Rubin, H., and Rubin, I., (2005). Qualitative Interviewing: The Art of Hearing Data, Thousand Oaks, CA.
49. Schwaber, K., and Beedle, M., (2002). Agile Software Development with Scrum, Prentice Hall, NJ, USA.
50. Silverman, D., (1998). Qualitative Research: Meaning or Practice. Information Systems Journal, (8:1): 3-20.
51. Sutherland, J., (2001). Agile Can Scale: Inventing and Reinventing SCRUM in Five Companies. Cutter IT Journal, (14:12): 5-11.
52. Takeuchi, H., and Nonaka, I., (1986). The New Product Development Game. Harvard Business Review, (64:1): 137-146.
53. VersionOne. (2009). State of Agile Development Survey 2009. Retrieved 31 March 2010 at http://pm.versionone.com/StateofAgileSurvey.html.
54. Wageman, R., (1997). Critical Success Factors for Creating Superb Self-Managing Teams. Organizational Dynamics, (26:1): 49-61.
55. Wageman, R., Fisher, C., M., and Hackman, J. R., (2009). Leading Teams when the Time is Right: Finding the Best Moments to Act. Organizational Dynamics, (38:3): 192-203.
56. Walsh, K. R., and Schneider, J., (2002). The role of Motivation and risk behaviour in software development success. Information Research, (7:3): 15.
57. Wengraf, T., (2001). Qualitative Research Interviewing, Sage Publications, London, UK.
58. Whitworth, E., and Biddle, R., Motivation and Cohesion in Agile Teams, Proceedings of the 8th International Conference, XP 2007, Como, Italy, June 18-22, 2007, pp. 62-69.
59. Whyte, G., (1989). Groupthink Reconsidered. The Academy of Management Review, (14:1): 40-56.
60. Yin, R., (2003). Case Study Research: Design and Methods, Thousand Oaks, CA.
61. Yin, R. K., (2008). Case Study Research: Design and Methods, (4th ed.), Sage Publications, Thousand Oaks, CA, USA
62. Zawacki, R. A., (1992). Motivating the IS People of the Future. Information Systems Management, (9:2): 73-75.