The development of high quality technical systems is an ongoing important element of information systems success. This paper investigates the current practice of information technology project configuration from a management viewpoint. It is based on a series of semi-structured interviews across a range of medium to large organizations in the UK, including both users and providers of IT services. It finds that project requirements, strategic IT policies, risk management, pragmatic considerations, the managed exploitation of experience and the managed adoption of new technologies drive individual project configuration. The paper proposes a new integrated model that explicitly identifies the drivers of project configuration management. It illustrates the model using a published case study and generates directions for further research and implications for practitioners.
Get full access to this article
View all access options for this article.
References
1.
BallantineJ., BonnerM., LevyM., MartinA., MunroI., and PowellP. (1996). The 3-D model of information systems success: the search for the dependent variable continues. Information Resource Management Journal, 9(4), 5–14.
2.
BroadbentM., WeillP., and NeoB.S. (1999). Strategic context and patterns of IT infrastructure capability. Journal of Strategic Information Systems, 8(2), 157–87.
3.
CurtisB., KrasnerH., and IscoeN. (1988). A field study of the software design process for large systems. Communications of the ACM, 31(11), 1268–87.
4.
DeLoneW.H., and McLeanE.R. (1992). Information systems success: the quest for the dependent variable. Information Systems Research, 3(1), 60–95.
5.
EarlM.J. (1989). Management Strategies for Information Technology (Prentice Hall Hevel Hempstead, New York; London).
6.
EarlM.J. (1992). Putting information technology in its place: a polemic for the nineties. Journal of Information Technology, 7, 100–8.
7.
Ewusi-MensahK., and PrzasnyskiZ. (1994). Factors contributing to the abandonment of information systems development projects. Journal of Information Technology, 9, 185–201.
8.
FeenyD., and WillcocksL.P. (1999). Rethinking cap abilities and skills in the information systems function. In Rethinking Management Information Systems: An Interdisciplinary Perspective, CurrieW., and GalliersR.D. (eds) (Oxford University Press, Oxford), pp. 444–73.
9.
FitzgeraldB. (1996). Formalized systems development methodologies: a critical perspective. Information Systems Journal, 6, 3–23.
10.
FitzgeraldB. (1997). The use of systems development methodologies in practice: a field study. Information Systems Journal, 7, 201–12.
11.
FitzgeraldB. (1998). An empirical investigation into the adoption of systems development methodologies. Information and Management, 34, 317–28.
12.
FitzgeraldG., PhilippedesA., and ProbertS. (1999). Information systems development, maintenance and enhancement: findings from a UK study. International Journal of Information Management, 19, 319–28.
13.
GalliersR.D. (1991a). Choosing appropriate information systems research approaches: a revised taxonomy. In Information Systems Research: Contemporary Approaches and Emergent Traditions, NissenH.-E., KleinH.K., and HirscheimR. (eds) (North-Holland, Amsterdam), pp. 327–45.
14.
GalliersR.D. (1991b). Strategic information systems planning: myths, reality and guidelines for successful implementation. European Journal of Information Systems, 1(1), 55–64.
15.
GalliersR.D., and SutherlandA.R. (1991). Information systems management and strategy formulation: the ‘stages of growth’ model revisited. Journal of Information Systems (renamed Information Systems Journal), 1, 89–114.
16.
GalliersR.D., SwanJ., NewellS., and RobertsonM. (1996). The Information Challenge: Making Your IT Investment Pay Off (Hot Topics Briefing Paper, Warwick Business School, Coventry, UK).
17.
GuntonT. (1989). Infrastructure: Building a Framework for Corporate Information Handling (Prentice Hall New York, London).
18.
HarrisT., RothwellJ.W., and LloydP.T.L. (1999). Experiences in reusing technical reference architectures. IBM Systems Journal, 38(1), 98–117.
19.
HoC.-F. (1996). Information technology implementation strategies for manufacturing organizations. A strategic alignment approach. International Journal of Operations and Production Management, 16(7), 77–100.
20.
KleinH.K., and MyersM. (1999). A set of principles for conducting and evaluating interpretive field studies in information systems. MIS Quarterly, 23(1), 67–94.
21.
LacityM., and HirschheimR. (1993). Information Systems Outsourcing: Myths, Metaphors and Realities (John Wiley & Sons, Chichester).
22.
LacityM.C., and WillcocksL.P. (1998). An empirical investigation of information technology sourcing practices: lessons from experience. MIS Quarterly, 22(3), 363–408.
23.
LeavittH.J. (1964). Applied organization change in industry: structural, technical and human approaches. In New Perspectives in Organizational Research, LeavittH.J. (ed.) (John Wiley, Chichester), pp. 55–71.
24.
LeeA.S. (1999). Researching MIS. In Rethinking Management Information Systems: An Interdisciplinary Perspective, CurrieW., and GalliersR.D. (eds) (Oxford University Press, Oxford), pp. 7–27.
25.
LyytinenK., and HirschheimR. (1987). Information systems failures: a survey and classification of the empirical literature. Oxford Surveys in Information Technology, 4, 257–309.
26.
LyytinenK., MathiassenL., and RopponenJ. (1996). A framework for software risk management. Journal of Information Technology, 11(4), 275–85.
27.
McFarlanW. (1982). Portfolio approach to information systems. Journal of Systems Management, 33(1), 12–19.
28.
MarkusM.L., AxlineS., PetrieD., and TanisS.C. (2000). Learning from adopters’ experiences with ERP: problems encountered and success achieved. Journal of Information Technology, 15(4), 245–65.
29.
MartinA., and ChanM. (1996). Information systems project redefinition in New Zealand: will we ever learn?Australian Computer Journal, 28(1), 27–40.
30.
MeredithJ.R., and MantelS.J.Jr. (2000). Project Management: A Managerial Approach, 4th edn (Wiley, New York), p. 100.
31.
PressmanR.S. (1997). Software Engineering: A Practitioner's Approach, 4th edn (McGraw-Hill, New York; London).
32.
RedmillF. (1997). Software Projects: Evolutionary vs Big-Bang Delivery (Wiley, Chichester).
33.
RossJ. (1999). Dow Corning Corporation: business processes and information technology. Journal of Information Technology, 14, 253–66.
34.
RussoN.L., and StoltermanE. (2000). Exploring the assumptions underlying information systems me thodologies: their impact on past, present and future ISM research. Information Technology & People, 13(4), 313–27.
35.
SawyerS. (2000). Packaged software: implications of the differences from custom approaches to software development. European Journal of Information Systems, 9, 47–58.
36.
Scott-MortonM.S. (ed.) (1991). The Corporation of the 1990s (Oxford University Press, Oxford).
37.
SeddonP.B. (1997). A respecification and extension of the DeLone and McLean model of IS success. Information Systems Research, 8, 240–53.
SomogyiE.K., and GalliersR.D. (1987). Applied information technology: from data processing to strategic information systems. Journal of Information Technology, 2(1), 30–41.
40.
StamM., and MollemanE. (1999). Matching the demand for and supply of IT professionals: towards a learning organization. International Journal of Manpower, 20(6), 375–87.
41.
StarS.L. (1992). The Trojan door: organizations, work, and the ‘open black box’. Systems Practice, 5(4), 395–410.
42.
SubramanianA., and LacityM.C. (1997). Managing client/server implementations: today's technology, yesterday's lessons. Journal of Information Technology, 12(3), 169–86.
43.
TruexD., BaskervilleR., and TravisJ. (2000). A methodical systems development: the deferred meaning of systems development methods. Accounting Management and Information Technologies, 10, 53–79.
44.
WalshamG. (1995). Interpretive case studies in IS research: nature and method. European Journal of Information Systems, 4(2), 74–81.
45.
WardJ., and GriffithsP. (1996). Strategic Planning for Information Systems, 2nd edn (Wiley, Chichester).
46.
WeickK. (1995). What theory is not: theorizing is. Administrative Science Quarterly, 40, 385–90.
47.
WexelblatR.L., and SrinivasanN. (1999). Planning for information technology in a federated organization. Information and Management, 35(5), 265–82.
48.
WillcocksL.P., and GriffithsC. (1994). Risk of failure in large-scale information technology projects. Technological Forecasting and Social Change, 47(2), 205–8.
49.
WillcocksL.P., and LacityM.C. (eds) (1998). Strategic Sourcing of Information Systems: Perspectives and Practices (Wiley, Chichester).
50.
YettonP., MartinA., SharmaR., and JohnstonK. (2000). A model of information systems development project performance. Information Systems Journal, 10(4), 263–89.
51.
YinR.K. (1994). Case Study Research: Design and Method, 2nd edn (Sage Publications, Beverly Hills, CA).
