Agile drivers, capabilities, and value: An over-arching assessment framework for systems development

Agile Information Systems: Conceptualization, Construction, and Management

Volumn , Issue , 2006, Pages 207-221

  Conboy, Kieran ^a   Fitzgerald, Brian ^a  

^a UNIVERSITY OF LIMERICK   (Ireland)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84905065481     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.4324/9780080463681     Document Type: Chapter

References (109)

1. Alleman, G. (2002). Agile project management methods for it projects. In The Story of Managing Projects: A Global, Cross-Disciplinary Collection of Perspectives (Carayannis, E. G. and Kwak, Y. H., eds.). Berkeley, CA: Greenwood Press.
2. Ambler, S. W. (2002). Agile Modelling: Best Practices for the Unified Process and Extreme Programming. New York: Wiley.
3. Agrawal. (2005). Modelling the metrics of lean, agile and agile supply chain: An ANP-based approach. European Journal of Operations Research, forthcoming.
4. Argyris, C. and Schon, D. (1978). Organizational Learning: A Theory of Action Perspective. Reading, MA: Addison-Wesley.
5. Ascher, H. (1965). Cost Quality Relationships in the Air Frame Industry. Santa Monica, CA:Rand Corporation.
6. Auer, K. and Miller, R. (2002). Extreme Programming Applied: Playing to Win. Boston:Addison-Wesley.
7. Baskerville, R., Travis, J., and Truex, D. P. (1992). Systems without method: The impact of new technologies on information systems development projects. In Proceedings of the IFIP WG8.2 Working Conference on the Impact of Computer Supported Technologies on Information Systems Development (Kendall, K., DeGross, J., and Lyytinen, K., eds.), pp. 241-269. North Holland: Elsevier.
8. Beck, K. (1999). Extreme Programming Explained: Embrace Change. Boston: Addison Wesley.
9. Beer, M. and Walton, A. E. (1987). Organization change and development. Annual Review of Psychology, 38 (1), 339-367.
10. Boehm, B., Gray, T., and Seewaldt, T. (1984). Prototyping versus specifying: A multiproject experiment. IEEE Transactions on Software Engineering, SE-10 (3), 290-302.
11. Boehm, B. and Turner, R. (2003). Balancing Agility and Discipline: A Guide for the Perplexed. Boston: Addison-Wesley.
12. Bowers, J., et al. (2002). Tailoring XP for Large Mission Critical Software Development. Paper presented at the XP/Agile Universe, Chicago, IL, August 4-7, 2002.
13. Brinkkemper, S. (1996). Method engineering: Engineering of information systems development methods and tools. Information and Software Technology, 38 (4), 275-280.
14. Burgess, T. F. (1994). Making the leap to agility: Defining and achieving agile manufacturing through business process redesign and business network redesign. International Journal of Operations & Production Management, 14 (11), 23-34.
15. Burton Swanson, E. (1988). Information System Implementation: Bridging the Gap between Design and Utilization. Homewood, IL: Irwin.
16. Cao, L., et al. (2004). How extreme does extreme programming have to be? In Adapting XP Practices to Large-Scale Projects, Thirty-Seventh Hawaii International Conference on System Sciences (HICSS-37 2004), January 5-8, 2004, Track 3-Volume 3 Big Island, HI, IEEE Computer Society.
17. Ciborra, C. and Lanzara, G. (1994). Formative contexts and information technology:Understanding the dynamics of innovations in organisations. Accounting, Management and Information Technology, 4 (2), 61-86.
18. Coad, P., de Luca, J., and Lefebre, E. (1999). Java Modeling in Color with UML: Enterprise Components and Process. New York: Prentice Hall.
19. Cockburn, A. (2001). Agile Software Development. Boston: Addison-Wesley.
20. Crispin, L. and House, T. (2002). Testing Extreme Programming. Boston: Addison-Wesley.
21. Cusick, J. (2003). How the work of software professionals changes everything. IEEE Software, 20 (3), 92-97.
22. Daft, R. and Weick, K. (1984). Toward a model of organizations as interpretation systems. Academy of Management Journal, 9 (2), 284-295.
23. Davis, G. B. (1982). Strategies for information requirements determination. IBM Systems Journal, 21 (1), 4-30.
24. Drucker, P. (1995). The information that executives truly need. Harvard Business Review, 73 (1), 54-62.
25. Dutton, J. and Jackson, S. (1987). Categorizing strategic issues: Links to organizational action. Academy of Management Review, 12 (1), 76-90.
26. Fenwick, J. (2003). Adapting XP to an Academic Environment by Phasing in Practices. Paper presented at the XP/Agile Universe 2003. New Orleans, LA.
27. Fitzgerald, B. (1994). The systems development dilemma: Whether to adopt formalised systems development methodologies or not? In Proceedings of the Second European Conference on Information Systems (W. Baets, ed.) (pp. 691-706). Holland: Nijenrode University Press.
28. Fitzgerald, B. (1996). Formalized systems development methodologies: A critical perspective. Information Systems Journal, 6 (1), 3-23.
29. Forte, G. (1997). Managing change for rapid development. IEEE Software, 14 (2), 120-122.
30. Fowler, M. (2000). Put your process on a diet. Software Development, 8 (12), 32-36.
31. Fowler, M. (2001). Extreme Programming Explained. Boston: Addison-Wesley.
32. Fowler, M. and Highsmith, J. (2001). The Agile manifesto. Software Development, August, 24-28, 2001.
33. Gerwin, D. (1993). Manufacturing flexibility: A strategic perspective. Management Science, 39 (4), 395-410.
34. Gibbs, W. (1994). Software's chronic crisis. Scientific American, 271 (3), 86-95.
35. Golden, W. and Powell, P. (2000). Towards a definition of flexibility: In search of the Holy Grail? Omega, 28, 373-384.
36. Goldman, S., Nagel, R., and Preiss, K. (1995). Agile Competitors and Virtual Organizations:Strategies for Enriching the Customer. New York: Von Nostrand Reinhold.
37. Goldman, S., et al. (1991). Iacocca Institute: 21st Century Manufacturing Enterprise Strategy:An Industry Led View (Vol. 1/2). Bethlehem, PA: Iacocca Institute.
38. Gould, P. (1997). What is agility? Manufacturing Engineer, 76 (1), 28-31.
39. Grimshaw, D. (1992). Towards a taxonomy of information systems: Or does anyone need a taxi. Journal of Information Technology, 7 (1), 30-36.
40. Gunasekaran, A. and Yusuf, Y. (2002). Agile manufacturing: A taxonomy of strategic and technological imperatives. International Journal of Production Research, 40 (6), 1357-1385.
41. Harker, S., Eason, K., and Dobson, J. (1993). The change and evolution of requirements as a challenge to the practice of software engineering. In Requirements Engineering, 1993, Proceedings of IEEE International Symposium on Requirements Engineering (C. Potts, ed.) (pp. 266-272).
42. Harmsen, F., Brinkkemper, S., and Oei, H. (eds.). (1994). Situational Method Engineering for Information System Project Approaches. North-Holland: Elsevier B.V.
43. Hoffer, J., George, J., and Valacich, J. (1999). Modern Systems Analysis and Design: Boston:Addison Wesley Longman.
44. Hong, M., Payander, S., and Gruver, W. (1996). Modelling and analysis of flexible fixturing systems for agile manufacturing. The IEEE International Conference on Systems, Management and Cybernetics, October 1996, Beijing, China.
45. Huber, G. (1982). Organizational information systems: Determinants of their performance and behavior. Management Science, 28 (2), 138-155.
46. Huber, G. (1996). Organizational learning: The contributing processes and the literatures. In Organizational Learning (Cohen, M. and Sproull, L., eds.), Thousand Oaks, CA: Sage.
47. Huber, G. and Daft, R. (1987). The information environments of organizations. In Handbook of Organizational Communication: An Interdisciplinary Perspective (pp. 130-164) (Jablin, F. et al., eds.). Newbury Park, CA: Sage.
48. James-Moore, S. (1996). Agility is easy but effective agile manufacturing is not. IEE Colloquium, 179 (1), 4-10.
49. Johnson, D. and Caristi, J. (2003). Extreme Programming and the Software Design Course. In Extreme Programming Perspectives (M. Marchesi, et al., eds.) pp. 261-271. Boston:Addison Wesley.
50. Jrgensen, M. (2004). Top-down and bottom-up expert estimation of software development effort. Information and Software Technology, 46 (1), 3-16.
51. Kahkonen, T. (2004). Agile Methods for Large Organizations: Building Communities of Practice. In Proceedings of the Agile Development Conference 2004, IEEE CS Press (T. Little, ed.), pp. 2-11.
52. Keil, M. (2003). Software project escalation and de-escalation: What do we know? Cutter IT Journal, 16 (12), 5-11.
53. Khaled, R., et al. (2004). System metaphor in "extreme programming": A semiotic approach. The Eighth International Workshop on Organisational Semiotics, June 23-24, 2005, Toulouse, France.
54. Kidd, P. (1996). Agile manufacturing: A strategy for the 21st century. IEE Colloquium (Vol. 74, 61EE). Stevenage, England.
55. Kircher, M. and Levine, D. (2001). The XP of Tao: Extreme programming of large open-source frameworks. In Extreme Programming Examined (Succi, G. and Marchesi, M., eds.). Boston:Addison-Wesley.
56. Kircher, M., et al. (2001). Distributed extreme programming. Paper presented at the Proceedings of XP2001-eXtreme Programming and Flexible Processes in Software Engineering. Villasimius, Sardinia, Italy, May 2001.
57. Klein, J. (1989). Parenthetic learning in organizations: Toward the unlearning of the unlearning model. Journal of Management Studies, 26 (1), 291-308.
58. Kruchten, P. (2000). The Rational Unified Process: An Introduction. Boston: Addison Wesley Longman.
59. Kumar, K. and Welke, R. J. (1992). Methodology engineering: A proposal for situationspecific methodology construction. In Challenges and Strategies for Research in Systems Development (Cotterman, W. and Senn, J, eds.), pp. 257-269. Chichester, UK:Wiley.
60. Kussmaul, C., Jack, R., and Sponsler, B. (2004). Outsourcing and Offshoring with Agility:A Case Study. Paper presented at the XP/Agile Universe, Calgary, Canada, August 2004.
61. Latour, B. (1988). The Pasteurization of France. Boston: Harvard University Press.
62. Latour, B. and Woolgar, S. (1979). Laboratory Life: The Social Construction of Scientific Facts. Beverly Hills, CA: Sage.
63. Lederer, A. and Prasad, J. (1991). The validation of a political model of information systems development cost estimating. In Proceedings of the 1991 Special Interest Group on Computer Personnel Research Annual Conference, April 8-9, 1991 (Ferratt, T., ed.), pp. 164-173, Athens, GA.
64. Levitt, B. and March, J. (1988). Organizational learning. Annual Review of Sociology, 14, 319-340.
65. Lindvall, M., et al. (2004). Agile software development in large organizations. IEEE Computer, 37 (12), 26-34.
66. Lounamaa, P. and March, J. (1987). Adaptive coordination of a learning team. Management Science, 33 (1), 107-123.
67. Lyytinen, K. and Robey, D. (1999). Learning failure in information systems development. Information Systems Journal, 9 (2), 85-101.
68. March, J. and Sevon, G. (1984). Gossip, information and decision-making. In Advances in information processing in organizations (Sproull, L. and Larkey, P., eds.). Greenwich, CT:JAI.
69. Mathiassen, L. and Purao, S. (2002). Educating reflective systems developers. Information Systems Journal, 12 (1), 81-102.
70. McConnell, S. (1998). The power of process. IEEE Computer, 31 (5), 100-102.
71. McDowell, C., Werener, L., and Bullock, H. (2003). The Impact of Pair Programming on Student Performance, Perception and Persistence. In Proceedings of the Twenty-Fifth International Conference on Software Engineering, May 3-10 (Clarke, L., Dillon, L., and Tichy, W., eds.) (pp. 222-230), Portland, OR.
72. Meier, R. (1963). Communication overload: Proposals from the study of a university library. Administrative Science Quarterly, 4 (1), 521-544.
73. Melnik, G. and Mauer, F. (2003). Agile methods in learning environments: Lessons learned. Paper presented at the XP/Agile Universe, 2003, New Orleans, LA.
74. Naylor, J., Naim, M., and Berry, D. (1999). Leagility: Integrating the lean and agile manufacturing paradigm in the total supply chain. Engineering Costs and Production Economics, 62 (1), 107-118.
75. Ohno, T. (1988). The Toyota Production System: Beyond Large Scale Production. Portland, OR:Productivity Press.
76. Olle, T., et al. (1991). Information Systems Methodologies: A Framework for Understanding:Boston: Addison-Wesley.
77. Pfleeger, S. (2002). What software engineering can learn from soccer. IEEE Software, 19 (6), 64-65.
78. Poole, C. and Huisman, J. (2001). Using extreme programming in a maintenance environment. IEEE Software, 18 (6), 42-50.
79. Poppendieck, M. (2001). Lean programming. Software Development, 9 (5), 71-75.
80. Pressman, R. (1997). Software Engineering: A Practitioner's Approach. New York: McGraw-Hill.
81. Rasmusson, J. (2003). Introducing XP into greenfield projects: Lessons learned. IEEE Computer, 20 (3), 21-28.
82. Salaway, G. (1997). An organizational learning approach to information systems development. MIS Quarterly, 11 (2), 245-264.
83. Schwaber, K. and Beedle, M. (2002). Agile Software Development with Scrum. New York:Prentice-Hall.
84. Sharifi, H. and Zhang, Z. (1999). A methodology for achieving agility in manufacturing organisations: An introduction. International Journal of Production Economics, 62 (1/2), 7-22.
85. Sharifi, H., et al. (2001). Agile manufacturing: A management and operational framework. In Proceedings of the Institution of Mechanical Engineers Part B-Journal of Engineering Manufacture, 215 (6), 857-869.
86. Sharp, J., Irani, Z., and Desai, S. (1999). Working towards agile manufacturing in the UK industry. International Journal of Production Economics, 62 (1), 155-169.
87. Stapleton, J. (1997). DSDM: Dynamic Systems Development Method. Harlow, England:Addison Wesley.
88. Stein, E. and Vandenbosch, B. (1996). Organizational learning during advanced systems development:Opportunities and obstacles. Journal of Management Information Systems, 13 (2), 115-136.
89. Stephens, M. and Rosenberg, D. (2003). Extreme Programming Refactored. Berkeley, CA:Apress.
90. Stotts, D., et al. (2003). Virtual teaming: Experiments and experiences with distributed pair programming. In Extreme Programming and Agile Methods: XP/Agile Universe 2003: Third XP Agile Universe Conference, New Orleans, LA, August 10-13, 2003: proceedings (Wells, D. and Maurer, F., eds.), pp. 129-141. Berlin: Springer.
91. Stratton, R. and Warburton, R. (2003). The strategic integration of agile and lean supply. International Journal of Production Economics, 85 (2), 183-198.
92. Succi, G. and Marchesi, M. (2001). Extreme Programming Examined. Reading, MA: Addison Wesley Longman.
93. Sullivan, C. H. (1985). Systems planning in the information age. Sloan Management Review, 26 (2), 3-11.
94. Symons, C. (1988). Function point analysis: Difficulties and improvements. IEEE Transactions on Software Engineering, 14 (1), 2-11.
95. Teague Jr., L. and Pidgeon, C. (1991). Structured Analysis Methods for Computer Information Systems. New York: Macmillan.
96. Towill, D. and Christopher, M. (2002). The supply chain strategy conundrum: To be lean or agile or to be lean and agile. International Journal of Logistics: Research and Applications, 5 (3), 299-309.
97. Towill, D., Childerhouse, P., and Disney, S. (2000). Speeding up the progress curve towards effective supply chain management. Supply Chain Management: An International Journal, 5 (3), 122-130.
98. Tsoi, H. (1999). A framework for management software project development. In Proceedings of the 1999 ACM Symposium on Applied Computing, San Antonio, Texas, pp. 593-597.
99. Vatter, W. (1947). The Fund Theory of Accounting and Its Implications for Financial Reports. Chicago: The University of Chicago Press.
100. Vokurka, R. and Fliedner, G. (1998). The journey toward agility. Journal of Industrial Management and Data Systems, 98 (4), 165-171.
101. Vonderembse, et al. (2006). Designing supply chains: Toward theory development. International Journal of Production Economics, 100 (2), 223-238.
102. Wainer, M. (2003). Adaptations for teaching software development with extreme programming:An experience report. Extreme Programming and Agile Methods-XP/Agile Universe 2003, pp. 199-207.
103. Wastell, D. (1999). Learning dysfunctions in information systems development: Overcoming the social defences with transitional objects. MIS Quarterly, 23 (4), 581-600.
104. Wastell, D. and Newman, M. (1996). Information system design, stress and organizational change in the ambulance services: A tale of two cities. Accounting, Management and Information Technology, 6 (4), 283-300.
105. Weber, R. (1987). Towards a theory of artifacts: A paradigmatic base for information systems research. Journal of Information Systems, 1, 3-19.
106. Winklhofer, H. (2002). Information systems project management during organizational change. Engineering Management Journal, 14 (2), 33-37.
107. Womack, J., Jones, D., and Roos, D. (1990). The machine that changed the world: Based on the Massachusetts Institute of Technology 5-million dollar 5-year study on the future of the automobile. New York: Rawson Associates.
108. Young, K., et al. (2001). Agile control systems. In Proceedings of the Institution of Mechanical Engineers, 215 (2), 189-195.
109. Yusuf, Y., Sarhadi, M., and Gunasekaran, A. (1999). Agile manufacturing: The drivers, concepts and attributes. International Journal of Production Economics, 62 (1-2), 33-43.