A Control Theory Perspective on Agile Methodology Use and Changing User Requirements

References

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