IS project alignment - A process perspective

Journal of Information Technology

Volumn 25, Issue 1, 2010, Pages 35-55

  Jenkin, Tracy A ^a   Chan, Yolande E ^a  

^a QUEEN S UNIVERSITY   (Canada)

Author keywords

Case studies; IS strategic alignment; Management of IS projects; Process management; Software development methodologies

Indexed keywords

EID: 77749254754     PISSN: 02683962     EISSN: 14664437     Source Type: Journal    
DOI: 10.1057/jit.2009.10     Document Type: Article

References (65)

1. Barki, H., Rivard, S. and Talbot, J. (1993). Toward an Assessment of Software Development Risk, Journal of Management Information Systems 10(2): 203-226.
2. Barki, H., Rivard, S. and Talbot, J. (2001). An Integrative Contingency Model of Software Project Risk Management, Journal of Management Information Systems 17(4): 37-69.
3. Behrens, S. (2007). Information Systems Diversity: Metaphor, meaning and myth, Proceedings of the Twenty-eighth International Conference on Information Systems (Montreal, Canada, 2007).
4. Benbasat, I., Goldstein, D.K. and Mead, M. (1987). The Case Research Strategy in Studies of Information-systems, MIS Quarterly 11(3): 369-386.
5. Benko, C. and McFarlan, F.W. (2003a). Connecting the Dots. Aligning Projects with Objectives in Unpredictable Times, Boston, MA: Harvard Business School Press.
6. Benko, C. and McFarlan, F.W. (2003b). Reducing Risk by Managing Chunks: Breaking projects into smaller, more manageable chunks reduces the risk of failure and allows companies to better align their project portfolios with corporate strategies, CIO 16(12): 1.
7. Berthon, P., Pitt, L., Ewing, M. and Carr, C.L. (2002). Potential Research Space in MIS: A framework for envisioning and evaluating research replication, extension, and generation, Information Systems Research 13(4): 416-427.
8. Boehm, B.W. (1989). Software Risk Management, Washington, D.C.: IEEE Computer Society Press.
9. Broadbent, M. and Weill, P. (1993). Improving Business and Information Strategy Alignment: Learning from the banking industry, IBM Systems Journal 32(1): 162-179.
10. Chan, Y.E. and Reich, B.H. (2007). IT Alignment: What have we learned? Journal of Information Technology 22: 297-315.
11. Chan, Y.E., Huff, S.L., Barclay, D.W. and Copeland, D.G. (1997). Business Strategic Orientation, Information Systems Strategic Orientation, and Strategic Alignment, Information Systems Research 8(2): 125-150.
12. Crossan, M.M., Lane, H.W. and White, R.E. (1999). An Organizational Learning Framework: From intuition to institution, Academy of Management Review 24(2): 522-537.
13. Cule, P.E. and Robey, D. (2004). A Dual-motor, Constructive Process Model of Organizational Transition, Organization Studies 25(2): 229-260.
14. Day, G.S. (2002). Managing the Market Learning Process, The Journal of Business & Industrial Marketing 17(4): 240-252.
15. Dube, L. and Pare, G. (2003). Rigor in Information Systems Positivist Case Research: Current practices, trends, and recommendations, MIS Quarterly 27(4): 597-635.
16. Eisenhardt, K.M. (1989). Building Theories from Case Study Research, Academy of Management Review 14(4): 532-550.
17. Gallupe, R.B. (2000). Images of Information Systems in the Early 21st Century, Communications of the Association for Information Systems 3(3): 1-17.
18. Hedberg, B. (1981). How Organizations Learn and Unlearn? in P.C. Nystrom and W.H. Starbuck (eds.) Handbook of Organizational Design, London: Oxford University Press.
19. Henderson, J.C. and Venkatraman, N. (1993). Strategic Alignment: Leveraging information technology for transforming organizations, IBM Systems Journal 32(1): 4-16.
20. Herbsleb, J., Zubrow, D., Godenson, D., Hayes, W. and Paulk, M. (1997). Software Quality and the Capability Maturity Model, Communications of the ACM 40(6): 30-40.
21. Hirschheim, R. and Sabherwal, R. (2001). Detours in the Path toward Strategic Information Systems Alignment, California Management Review 44(1): 87-108.
22. Hussin, H., King, M. and Cragg, P. (2002). IT Alignment in Small Firms, European Journal of Information Systems 11(2): 108-127.
23. 0s School of Business Working Paper.
24. Kearns, G.S. and Sabherwal, R. (2006). Strategic Alignment Between Business and Information Technology: A knowledge-based view of behaviours, outcome, and consequences, Journal of Management Information Systems 23(3): 129-162.
25. Keil, M. (1995). Pulling the Plug: Software project management and the problem of project escalation, MIS Quarterly 19(4): 421-447.
26. Kim, D.H. (1993). The Link between Individual and Organizational Learning, Sloan Management Review 35(1): 37-50.
27. Lee, A.S. (1989). A Scientific Methodology for MIS Case Studies, MIS Quarterly 13(1): 33-50.
28. Luftman, J. and Brier, T. (1999). Achieving and Sustaining Business-IT Alignment, California Management Review 42(1): 109-122.
29. Luftman, J. and Kempaiah, R. (2007). An Update on Business-IT Alignment: 'A line' has been drawn, MIS Quarterly Executive 6(3): 165-177.
30. Luftman, J. and Kempaiah, R. (2008). Key Issues for IT Executives 2007, MIS Quarterly Executive 7(2): 99-112.
31. Luftman, J.N., Lewis, P.R. and Oldach, S.H. (1993). Transforming the Enterprise: The alignment of business and information technology strategies, IBM Systems Journal 32(1): 198-221.
32. Mackenzie, K.D. (2000). Processes and Their Frameworks, Management Science 46(1): 110-125.
33. Markus, M.L. and Robey, D. (1988). Information Technology and Organizational Change: Causal structure in theory and research, Management Science 34(5): 583-598.
34. Microsoft (2002). Microsoft Solutions Framework White Paper, From the World Wide Web [www document] http://www.microsoft.com/msf (accessed 6th July 2006).
35. Morgan, G. (1997). Images of Organizations, 2nd edn, Thousand Oaks: Sage Publications.
36. Nelson, R.R. (2007). IT Project Management: Infamous failures, classic mistakes, and best practices, MIS Quarterly Executive 6(2): 67-78.
37. Newman, M. and Robey, D. (1992). A Social Process Model of User-Analyst Relationships, MIS Quarterly 16(2): 249-266.
38. Nidumolu, S. (1995). The Effect of Coordination and Uncertainty on Software Project Performance: Residual performance risk as an intervening variable, Information Systems Research 6(3): 191-219.
39. Nidumolu, S.R. (1996a). A Comparison of the Structural Contingency and Risk-based Perspectives on Coordination in Software-development Projects, Journal of Management Information Systems 13(2): 77-113.
40. Nidumolu, S.R. (1996b). Standardization, Requirements Uncertainty and Software Project Performance, Information & Management 31(3): 135-150.
41. Orlikowski, W.J. (2002). Knowing in Practice: Enabling a collective capability in distributed organizing, Organization Science 13(3): 249-273.
42. Palmer, S.R. and Fetsing, J.M. (2002). A Practical Guide to Feature Driven Development, Upper Saddle River, NJ: Prentice Hall PTR.
43. Papp, R. (1999). Business-IT Alignment: Productivity paradox payoff? Industrial Management & Data Systems 99(8): 367-373.
44. Parker, M.M., Benson, R.J. and Trainor, H.E. (1988). Information Economics. Linking Business Performance to Information Technology, Englewood Cliffs, NJ: Prentice Hall.
45. PMI (2000). A Guide to the Project Management Body of Knowledge: PMBOK guide, 2000 edn, Pennsylvania: Project Management Institute, Inc.
46. PMI (2004). A Guide to the Project Management Body of Knowledge: PMBOK guide, 3rd edn, Pennsylvania: Project Management Institute, Inc.
47. Poole, M.S., Van de Ven, A.H., Dooley, K. and Holmes, M.E. (2000). Organizational Change and Innovation Processes, New York: Oxford University Press.
48. Reich, B.H. and Benbasat, I. (2000). Factors that Influence the Social Dimension of Alignment between Business and Information Technology Objectives, MIS Quarterly 24(1): 81-113.
49. Ross, J.W. (2003). Creating a Strategic IT Architecture Competency: Learning in stages, MIS Quarterly Executive 2(1): 31-43.
50. Sabherwal, R. and Chan, Y.E. (2001). Alignment between Business and IS Strategies: A study of prospectors, analyzers and defenders, Information Systems Research 12(1): 11-33.
51. Sabherwal, R. and Robey, D. (1995). Reconciling Variance and Process Strategies for Studying Information System Development, Information Systems Research 6(4): 303-327.
52. Sabherwal, R., Hirschheim, R. and Goles, T. (2001). The Dynamics of Alignment: Insights from a punctuated equilibrium model, Organization Science 12(2): 179-197.
53. Samaddar, S. and Kadiyala, S. (2006). Information Systems Outsourcing: Replicating an existing framework in a different cultural context, Journal of Operations Management 24: 910-931.
54. Schultz, M. (1994). On Studying Organizational Cultures: Diagnosis and understanding, Berlin: Walter de Gruyter.
55. Strauss, A. and Corbin, J. (1990). Basics of Qualitative Research. Grounded Theory Procedures and Techniques, Newbury Park, CA: Sage Publications Inc.
56. Taylor, F.W. (1911). The Principles of Scientific Management, New York: Harper Bros.
57. Turner, J.A. (1992). A Comparison of the Process of Knowledge Elicitation with that of Information Requirements Determination, in E.W.W. Cotterman and J.A. Senn (eds.) Challenges and Strategies for Research in Systems Development, New York: John Wiley & Sons Ltd.
58. Van Der Zee, J.T.M. and De Jong, B. (1999). Alignment Is Not Enough: Integrating business and information technology management with the balanced business scorecard, Journal of Management Information Systems 16(2): 137-156.
59. Wallace, L., Keil, M. and Rai, A. (2004). How Software Project Risk Affects Project Performance: An investigation of the dimensions of risk and an exploratory model, Decision Sciences 35(2): 289-321.
60. Wastell, D.G. (1996). The Fetish of Technique: Methodology as a social defence, Information Systems Journal 6(1): 25-40.
61. Wastell, D.G. (1999). Learning Dysfunctions in Information Systems Development: Overcoming the social defenses with transitional objects, MIS Quarterly 23(4): 581-600.
62. Wastell, D.G. and Newman, M. (1993). The Behavioral Dynamics of Information System Development: A stress perspective, Accounting, Management and Information Technology 3(2): 121-148.
63. Weick, K.E. and Roberts, K.H. (1993). Collective Mind in Organizations: Heedful interrelating on flight decks, Administrative Science Quarterly 38(3): 357-381.
64. Yin, R.K. (1994). Case Study Research: Design and methods, Thousand Oaks, CA: Sage Publications.
65. Zmud, R.W. (1980). Management of Large Software Development Efforts, MIS Quarterly 4(2): 45-55.