A control theory perspective on agile methodology use and changing user requirements

Information Systems Research

Volumn 20, Issue 3, 2009, Pages 377-399

  Maruping, Likoebe M ^a   Venkatesh, Viswanath ^a   Agarwal, Ritu ^b  

^a UNIVERSITY OF ARKANSAS   (United States)

^b UNIVERSITY OF MARYLAND   (United States)

Author keywords

Agile methodologies; Agility; Control theory; Requirements uncertainty; Software development; Teams

Indexed keywords

COMPUTER CONTROL; HUMAN RESOURCE MANAGEMENT; MANAGERS; PROJECT MANAGEMENT; QUALITY CONTROL; SOFTWARE DESIGN; SOFTWARE ENGINEERING; SOFTWARE TESTING;

AGILE DEVELOPMENT METHODOLOGIES; AGILE METHODOLOGIES; AGILITY; REQUIREMENTS CHANGE; REQUIREMENTS UNCERTAINTIES; SOFTWARE DEVELOPER; SOFTWARE DEVELOPMENT ENVIRONMENT; TEAMS;

CONTROL THEORY;

EID: 70149092236     PISSN: 10477047     EISSN: 15265536     Source Type: Journal    
DOI: 10.1287/isre.1090.0238     Document Type: Article

References (85)

1. Aiken, L. S., S. G. West. 1991. Multiple Regression: Testing and Interpreting Interactions. Sage, London.
2. Ang, S., S. A. Slaughter. 2001. Work outcomes and job design for contract versus permanent information systems professionals on software development teams. MIS Quart. 25(3) 321-350.
3. Aoyama, M. 1998. Web-based agile software development. IEEE Software 15(6) 56-65.
4. Bailyn, L. 1985. Autonomy in the industrial R&D laboratory. Human Resource Management 24 129-146.
5. Banker, R. D., S. M. Datar, C. F. Kemerer. 1991. A model to evaluate variables impacting productivity on software maintenance projects. Management Sci. 37(1) 1-18.
6. Banker, R. D., G. B. Davis, S. A. Slaughter. 1998. Software development practices, software complexity, and software maintenance performance: A field study. Management Sci. 44(4) 433-450.
7. Barki, H., J. Hartwick. 2001. Interpersonal conflict and its management in information system development. MIS Quart. 25(2) 195-228.
8. Baron, R. M., D. A. Kenny. 1986. The moderator-mediator variable distinction in social psychological research: Conceptual, strategic, and statistical considerations. J. Personality Soc. Psych. 51(6) 1173-1182.
9. Baskerville, R., L. Levine, J. Pries-Heje, B. Ramesh, S. A. Slaughter. 2002. Balancing quality and agility in Internet speed software development. L. Applegate, R. Galliers, J. I. DeGross, eds. Proc. 23rd Internat. Conf. Inform. Systems, Barcelona, Spain, 859-864.
10. Beath, C. M., W. J. Orlikowski. 1994. The contradictory structure of systems development methodologies: Deconstructing the IS-user relationship in information engineering. Inform. Systems Res. 5(4) 350-377.
11. Beck, K. 1999. Embracing change with extreme programming. IEEE Comput. 32 70-77.
12. Beck, K. 2000. Extreme Programming Explained. Addison-Wesley, Reading, MA.
13. Beck, K. 2003. Test-Driven Development by Example. Addison-Wesley, Reading, MA.
14. Bieman, J. 2002. Risks to software quality. Software Quality J. 10(1) 7-9.
15. Bliese, P. D. 2000. Within-group agreement, non-independence, and reliability: Implications for data aggregation and analysis. K. J. Klein, S. W. J. Kozlowski, eds. Multilevel Theory, Research, and Methods in Organizations. Jossey-Bass, San Fransisco, 349-381.
16. Boehm, B. W. 1981. Software Engineering Economics. Prentice-Hall, Upper Saddle River, NJ.
17. Boehm, B. W. 1991. Software risk management: Principles and practices. IEEE Software 8(1) 32-41.
18. Boehm, B. W., R. Turner. 2005. Management challenges to implementing agile processes in traditional development organizations. IEEE Software 22(5) 30-39.
19. Brooks, F. P., Jr. 1987. No silver bullet: Essence and accidents of software engineering. Computer 20(4) 10-19.
20. Byrd, T. A., D. E. Turner. 2000. Measuring the flexibility of information technology infrastructure: Exploratory analysis of a construct. J. Management Inform. Systems 17(1) 167-208.
21. Card, D. N. 1992. Designing software for producibility. J. Systems Software 17 219-225.
22. Card, D. N., R. L. Glass. 1990. Measuring Software Design Quality. Prentice-Hall, Englewood Cliffs, NJ.
23. Carte. T. A., C. J. Russell. 2003. In pursuit of moderation: Nine common errors and their solutions. MIS Quart. 27(3) 479-501.
24. Chan, D. 1998. Functional relations among constructs in the same content domain at different levels of analysis: A typology of composition models. J. Appl. Psych. 83 234-246.
25. Choudhury, V., R. Sabherwal. 2003. Portfolios of control in outsourced software development projects. Inform. Systems Res. 14(3) 291-314.
26. Coad, P., J. De Luca, E. Lefebre. 1999. Java Modeling in Color. Prentice-Hall, Englewood Cliffs, NJ.
27. Cockburn, A. 2001. Agile Software Development. Addison-Wesley, Reading, MA.
28. Cohen, S. G., D. E. Bailey. 1997. What makes teams work? Group effectiveness research from the shop floor to the executive suite. J. Management 23 239-290.
29. Cohen, S. G., G. E. Ledford, G. M. Spreitzer. 1996. A predictive model of self-managing work team effectiveness. Human Relations 49 643-676.
30. Conboy, K. 2009. Agility from first principles: Reconstructing the concept of agility in information systems development. Inform. Systems Res. 20(3) 329-354.
31. Curtis, B., H. Krasner, N. Iscoe. 1988. A field study of the software design process for large systems. Comm. ACM 31(11) 1268-1287.
32. Cusumano, M. A., D. B. Yoffie. 1999. Software development on Internet time. IEEE Comput. 32(10) 60-69.
33. Darcy, D. P., S. A. Slaughter, C. F. Kemerer, J. E. Tomayko. 2005. The structural complexity of software: An empirical test. IEEE Trans. Software Engrg. 31(11) 982-995.
34. DeVellis, R. F. 2003. Scale Development: Theory and Applications. Sage, Thousand Oaks, CA.
35. Duncan, N. B. 1995. Capturing flexibility of information technology infrastructure: A study of resource characteristics and their measure. J. Management Inform. Systems 12(2) 37-57.
36. Eisenhardt, K. M. 1985. Control: Organizational and economic approaches. Management Sci. 31(2) 134-149.
37. Fitzgerald, B. 2000. Systems development methodologies: The problem of tenses. Inform. Tech. People 13 13-22.
38. Fitzgerald, B., G. Hartnett, K. Conboy. 2006. Customising agile methods to software practices at Intel Shannon. Eur. J. Inform. Systems 15 200-213.
39. Fowler, M. 2005. The new methodology. Retrieved May 26, 2007, http://www.martinfowler.com/articles/newMethodology.html.
40. Fowler, M., J. Highsmith. 2001. Agile methodologists agree on something. Software Development 9 28-32.
41. Gefen, D., M. Keil. 1998. The impact of developer responsiveness on perceptions of usefulness and ease of use: An extension of the technology acceptance model. DATABASE Adv. Inform. Systems 29(2) 35-49.
42. Gerwin, D., L. Moffat. 1997. Withdrawal of team autonomy during concurrent engineering. Management Sci. 43(9) 1275-1287.
43. Greene, W. H. 1997. Econometric Analysis, 3rd ed. MacMillan Publishing Company, New York.
44. Guinan, P. J., J. G. Cooprider, S. Faraj. 1998. Enabling software development team performance during requirements definition: A behavioral versus technical approach. Inform. Systems Res. 9(2) 101-125.
45. Hackman, J. R. 1986. The psychology of self-management in organizations. M. S. Pallack, R. O. Perloff, eds. Psychology and Work: Productivity, Change, and Employment. American Psychological Association, Washington, DC, 89-136.
46. Henderson, J. C., S. Lee. 1992. Managing I/S design teams: A control theories perspective. Management Sci. 38(6) 757-777.
47. Highsmith, J., A. Cockburn. 2001. Agile software development: The business of innovation. IEEE Comput. 34(9) 120-122.
48. Hoorn, J. F., E. A. Konijn, H. van Vliet, G. van der Veer. 2007. Requirements change: Fears dictate the must haves; desires the won't haves. J. Systems Software 80(3) 328-355.
49. Humphrey, W. S. 1995. A Discipline for Software Engineering. Addison-Wesley, Reading, MA.
50. Iansiti, M., A. MacCormack. 1997. Developing products on Internet time. Harvard Bus. Rev. 75(5) 108-117.
51. James, L. R., R. G. Demaree, G. Wolf. 1984. Estimating within group interrater reliability with and without response bias. J. Appl. Psych. 69 219-229.
52. Jaworski, B. J. 1988. Toward a theory of marketing control: Environmental context, control types, and consequences. J. Marketing 52 23-39.
53. Kemerer, C. F. 1995. Software complexity and software maintenance: A survey of empirical research. Ann. Software Engrg. 1(1) 1-22.
54. Kirkman, B. L., D. L. Shapiro. 2001. The impact of cultural values on job satisfaction and organizational commitment in self-managing work teams: The mediating role of employee resistance. Acad. Management J. 44(3) 557-569.
55. Kirsch, L. J. 1996. The management of complex tasks in organizations: Controlling the systems development process. Organ. Sci. 7(1) 1-21.
56. Kirsch, L. J. 1997. Portfolios of control modes and IS project management. Inform. Systems Res. 8(3) 215-239.
57. Kirsch, L. J. 2004. Deploying common systems globally: The dynamics of control. Inform. Systems Res. 15(4) 374-395.
58. Kirsch, L. J., V. Sambamurthy, D.-G. Ko, R. L. Purvis. 2002. Controlling information systems development projects: The view from the client. Management Sci. 48(4) 484-498.
59. Klein, K. J., F. Dansereau, R. J. Hall. 1994. Levels issues in theory development, data collection, and analysis. Acad. Management Rev. 19(2) 195-229.
60. Langfred, C. W. 2004. Too much of a good thing? Negative effects of high trust and individual autonomy in self-managing teams. Acad. Management J. 47 358-399.
61. Larman, C. 2003. Agile and Iterative Development: A Manager's Guide. Addison-Wesley, Boston, MA.
62. Lee, G., W. Xia. 2005. The ability of information systems development project teams to respond to business and technology changes: A study of flexibility measures. Eur. J. Inform. Systems 14 75-92.
63. MacCormack, A., R. Verganti, M. Iansiti. 2001. Developing products on "Internet time": The anatomy of a flexible development process. Management Sci. 47(1) 133-150.
64. Manz, C. C., H. P. Sims, Jr. 1987. Leading workers to lead themselves: The external leadership of self-managing work teams. Admin. Sci. Quart. 32 106-128.
65. Maruping, L. M., R. Agarwal. 2004. Managing team interpersonal processes through technology: A task-technology fit perspective. J. Appl. Psych. 89(6) 975-990.
66. Mathiassen, L., T. Tuunanen, T. Saarinen, M. Rossi. 2007. A contingency model for requirements development. J. AIS 8(11) 569-597.
67. McCabe, T. J. 1976. A complexity measure. IEEE Trans. Software Engrg. 2(4) 308-320.
68. Nidumolu, S. 1995. The effect of coordination and uncertainty on software project performance: Residual performance risk as an intervening variable. Inform. Systems Res. 6(3) 191-219.
69. Nidumolu, S. R., M. Subramani. 2003. The matrix of control: Combining process and structure approaches to managing software development. J. Management Inform. Systems 20(3) 159-196.
70. Nosek, J. 1998. The case for collaborative programming. Comm. ACM 41(3) 105-108.
71. Ouchi, W. G. 1979. A conceptual framework for the design of organizational control mechanisms. Management Sci. 25(9) 833-848.
72. Podsakoff, P. M., S. B. MacKenzie, J.-Y. Lee, N. P. Podsakoff. 2003. Common method biases in behavioral research: A critical review of the literature and recommended remedies. J. Appl. Psych. 88(5) 879-903.
73. Poppendeick, M. 2001. Lean programming. Software Development 9 71-75.
74. Rising, L., N. S. Janoff. 2000. The Scrum software development process for small teams. IEEE Software 17(4) 26-32.
75. Ryan, T. Y. 1997. Modern Regression Analysis. Wiley, New York.
76. Schwaber, K., M. Beedle. 2002. Agile Software Development with Scrum. Prentice-Hall, Upper Saddle River, NJ.
77. Sillince, J. A. A., S. Mouakket. 1997. Varieties of political process during systems development. Inform. Systems Res. 8(4) 368-397.
78. Slaughter, S. A., L. Levine, R. Balasubramaniam, J. Pries-Heje, R. Baskerville. 2006. Aligning software processes with strategy. MIS Quart. 30(4) 891-918.
79. Standish Group. 2003. Chaos report. Accessed June 6, 2006, http://www.standishgroup.com.
80. Straub, D. W. 1989. Validating instruments in MIS research. MIS Quart. 13(2) 147-169.
81. Vessey, I. 1989. Toward a theory of computer program bugs: An empirical test. Internat. J. Man-Machine Stud. 30(3) 23-46.
82. Wageman, R. 1995. Interdependence and group effectiveness. Admin. Sci. Quart. 40 145-180.
83. Walz, D. B., J. J. Elam, B. Curtis. 1993. Inside a software design team: Knowledge acquisition, sharing, and integration. Comm. ACM 36(10) 63-77.
84. Weinberg, G. 1971. The Psychology of Computer Programming. Van Nostrand Reinhold, New York.
85. Zellner, A. 1962. An efficient method for estimating seemingly unrelated regressions and tests for aggregation bias. J. Amer. Statist. Assoc. 57 348-368.