AndersonJ.G. (1997). Clearing the way for physicians' use of clinical information systems.Communications of the ACM, 40 (8), 83–90.
2.
AndrioleS.J. and FreemanP.A. (1993). Software systems engineering: The case for a new discipline.Software Engineering Journal, 8 (3), 165–179.
3.
BariffM.L. and GinzbergM.J. (1982). MIS and the behavioural sciences: Research patterns and prescriptions.Data Base, Fall, 19–29.
4.
BeckhardR. and HarrisR. (1987). Organizational transitions.2nd ed.Reading, MA: Addison-Wesley.
5.
Benyon-DaviesP. (1997). Information systems failures and how to avoid them.London: Financial Times-Pitman.
6.
BlakeR.R.ShepardH.A. and MoutonJ.S. (1964). Managing intergroup conflict in industry.Houston, Tx: Gulf.
7.
BridgesW. (1991). Managing transitions: Making the most of change.Reading, MA: Addison-Wesley.
8.
BriggsP. (1996). Bosses fear IT, Say staff.Computing, 12th September, 33.
9.
BriggsP. (1997). Managers fall down on basics.Computing, 6th February, 35.
10.
BroderJ. (1997). How the IRS got left behind on the road ahead, New York Times, February 10.
11.
BurkeW.W. (1994). Organization development: A process of learning and changing, 2nd ed., Reading, MA: Addison-Wesley.
12.
BurkeW.W. (1997). The new agenda for organization development.Organizational Dynamics, Summer, 7–20.
13.
Cambridge Information Network (1999). Business feels the ERP heat.Computing, 27 May, 37–40.
14.
CleggC. W.AxtellC.DamodaranL.FarbeyB.HullR.Lloyd-JonesR.NichollsJ.SellR.TomlinsonC.AingerA., and StewartT. (1996). The performance of information technology and the role of human and organizational factors. United Kingdom: Report to the Economic and Social Research Council.
15.
CleggC.W. and KempN. (1986). Information technology: Personnel, where are you?Personnel Review, 15 (1), 8–15.
16.
CleggC.W. (1995). Psychology and information technology: The study of cognition in organizations.British Journal of Psychology, 85, 449–477.
17.
CleggC.W.WatersonP.E., and AxtellC.M. (1997). Software development: Some critical views.Behaviour and Information Technology, 16 (6), 359–362.
18.
CoelhoJ.D.JelassiT.KönigW.KrcmarH.O'CallaghanR. and SääksjärviM.(eds), (1996). Proceedings of the 4th European conference on information systems, Lisbon, Portugal, July 2–4.
19.
CoghlanD. (1998). The interlevel dynamics of information technology, Journal of Information Technology, 13 (2), 139–149.
20.
CoghlanD. (2000). Interlevel dynamics in clinical inquiry, Journal of Organizational Change Management, 13 (2), 190–200.
21.
CoghlanD. (2002). Facilitating learning and change: Perspectives on the helping process, Organization Development Journal, 20 (2), 116–119.
22.
CoghlanD and McDonaghJ. (2001). Research and practice in IT-enabled change: the case for clinical inquiry. In WoodmanR. W and PasmoreW.A. (eds.) Research in organizational change and development (vol. 13, pp. 195–211). Oxford: Elsevier.
23.
CroweT.J.Zayas-CastroJ.L.et al. (2002). Readiness assessment for enterprise resource planning.The Eleventh International Conference on the Management of Technology.
24.
DavenportT.H. (1994). Saving IT's soul: Human-centered information management.Harvard Business Review, March-April, 119–131.
25.
DeardenJ. (1972). MIS is a mirage.Harvard Business Review, January-February, 90–99.
26.
DrummondH. (1986). Escalation in decision making: The tragedy of taurus, Oxford: Oxford University Press.
27.
FlowersS. (1996). Software failure: Management failure. Chichester: John Wiley and Sons.
28.
GhoshalS. and GrattonL. (2002). Integrating the enterprise, Sloan Management Review, 44 (1), 31–38.
GoldenT. (1997). Does your IT manager make any sense?The Sunday Business Post, Computers in Business Supplement, February 23rd, 4.
31.
GrossN.StepanekM.PortO. and CareyJ. (1999). Software hell.Business Week, December 6, 38–44.
32.
HallahanS. (1998). Short-sighted attitude.Computing, February 19, 164–166.
33.
HeeksR.MundyD. and SalazarA. (1999). Why health care information systems succeed or fail, Information Systems for Public Sector Management, Working Paper Series, Paper #9, University of Manchester, Institute for Development Policy and Management.
34.
HeeksR.B. and DaviesA. (1999). Different approaches to information age reform. In HeeksR.B. (ed.), Reinventing government in the information age, London: Routledge.
35.
HurstB. (1991). Facilitating change: The key to success with information technology, Chief Information Officer Journal, Spring, 39–46.
36.
Isaac-HenryK. (1997). Management of information technology in the public sector. In Isaac-HenryK., PainterK., C. and BarnesC. (eds), Management in the public sector - Challenge and change, London: Thomson, 131–159.
37.
JamesG. (1997). IT fiascoes and how to avoid them.Datamation, 43 (11), 84–88.
38.
JohnsonJ. (1995). Chaos: The dollar drain of IT project failures. Application Development Trends, January, 41–47.
39.
JohnsonM. (1996). Bank group freezes £200m roll-out, Computing, April 25, 1.
40.
JonesR. (1997a). CSA plans to replace the ‘heartache' system early.Computing, April 3, 1.
41.
JonesR. (1997b). Hospital projects on the critical list, Computing, April 25, 8.
42.
KaneF. and WhitebloomS. (1993). Stock exchange boss resigns over computer fiasco, Guardian Weekly, March 21, 4.
43.
KearneyA.T. (1990). Barriers to the successful application of information technology. London: Department of Trade and Industry.
44.
KeenJ. (ed.) (1994). Information management in health services, Buckingham, England, Open University Press.
45.
Kirby-GreenF. (1993). Wessex man, Panorama, BBC News and Current Affairs, London, July 13,
46.
Korac-BoisvertN. and KouzminA. (1995). Transcending soft-core IT disasters in public sector organizations, Information Infrastructure and Policy, 4 (2), 131–161.
47.
Korn / Ferry International (1998). The changing role of the chief information officer. London: Korn / Ferry International in conjunction with the Financial Times.
48.
LeeJ. SiauK. and HongS. (2003). Enterprise integration with ERP and EAI, Communications of the ACM, 46 (2), 54–60.
49.
LippittG. and LippittR. (1978). The consulting process in action. San Diego: Pfeiffer.
50.
LongR.J. (1987). New office information technology: Human and managerial implications. London: Croom Helm.
51.
LowL. (2002). The integration imperative, CIO, August 15, 40–46.
52.
LucasH.C. (1975). Why information systems fail. New York: Columbia University Press.
53.
LuntP.J. and BarclayI. (1988). The importance of organizational considerations for the implementation of information technology.Journal of Information Technology, 3 (4), 244–250.
54.
MarkusM.L. and BenjaminR.I. (1997a). The magic bullet of IT-enabled change. Sloan Management Review, 38 (2), 55–68.
55.
MarkusM.L. and BenjaminR.I. (1997b). IT-enabled organizational change: New developments for IT specialists. In SauerC.YettonP.W., and Associates, (eds): Steps To The Future: Fresh Thinking on the Management of IT-Based Organizational Transformation. San Francisco: Jossey-Bass, 115–142.
56.
MartinB.L.BatchelderG.NewcombJ.RockartJ.F.YetterW.P. and GrossmanJ.H. (1995). The end of delegation? Information technology and the CEO.Harvard Business Review, September-October, 161–172.
57.
McAfeeA. (2003). When too much IT knowledge is a dangerous thing, Sloan Management Review, 44 (2), 83–89.
58.
McDermottL. (1984): The many faces of the OD professional, Training and Development Journal, February, 15–19.
59.
McDonaghJ. (1999). Exploring the role of executive management in shaping strategic change: The case of information technology.Unpublished PhD Dissertation, University of Warwick: England.
60.
McDonaghJ. (2000). Knowledge fragmentation and IT-enabled failure – A conspicuous relationship.Paper Presented to the INFORMS/KORMS Conference, Seoul, Korea, June18–21.
61.
McDonaghJ. (2003a). Surfacing hidden impediments to electronic service delivery, Working Paper, School of Business Studies, Trinity College, Dublin, Ireland.
62.
McDonaghJ. (2003b). Embracing the challenge of integrated change, Working Paper, School of Business Studies, Trinity College, Dublin, Ireland.
63.
McDonaghJ. and CoghlanD. (1999). Can OD help solve the IT dilemma? OD in IT-enabled change, Organization Development Journal, 17 (4), 41–48.
64.
McDonaghJ. and CoghlanD. (2000). Sustaining the dilemma with IT-enabled change – The fortituous role of academia, Journal of European Industrial Training, 24 (5), 297–304.
65.
McDonaghJ. and CoghlanD. (2001). The art of clinical inquiry in information technology-related change. In ReasonP. and BradburyH. (eds.) Handbook of Action Research. London: Sage372–378.
66.
McGinnJ. (1997). Men of faction.Computing, December 18, 28–29.
67.
McNurlinB. (2001). Will users of ERP stay satisfied?” Sloan Management Review, 42 (2), 13.
68.
MontealegreR.KnoopC.I. and ApplegateL.M. (1996a). BAE automated systems (A): Denver International Airport baggage-handling system, Harvard Business School Case Study N9-396-311, April 12, Harvard Business School, Boston, MA.
69.
MontealegreR.KnoopC.I.NelsonJ. and ApplegateL.M. (1996b). BAE automated systems (B): Implementing the Denver International Airport baggage-handling system, Harvard Business School Case Study N9-396-312, April 26, Harvard Business School, Boston, MA.
70.
MoreE. (1990). Information systems: People issues.Journal of Information Science, 16, 311–320.
71.
NadlerD.A. (1998). Champions of Change. San Francisco: Jossey-Bass.
72.
OECD (2001). The hidden threat to E-government – avoiding large government IT failures. Organization for Economic Cooperation and Development, Public Management Policy Brief No. 8, March.
73.
OzE. (1994). When professional standards are lax, The Confirm failure and its lessons.Communications of the ACM, 37 (10), 29–36.
74.
PareG. and ElamJ. J. (1988). Introducing information technology in the clinical setting, International Journal of Technology Assessment in Health Care, 14 (2), 331–343.
75.
Performance and Innovation Unit (2000): Electronic government services for the 21st century, London: Cabinet Office.
76.
PlunkettS. (1991). Westpac abandons high-tech hopes, Business Review Weekly, November 8, pp. 26–27.
77.
PorterM.E. (2001). Strategy and the internet.Harvard Business Review, 79 (1), 63–78.
78.
PrahaladC.K. and KrishnanM.S. (2002). The dynamic synchronization of strategy and information technology, Sloan Management Review, 43 (4), 24–33.
79.
RangerS. (2000). Why government IT projects fail.Computing, 12 October, 1.
80.
RashfordN.S. and CoghlanD. (1994). The dynamics of organizational levels. Reading, MA: Addison-Wesley.
81.
RigbyD.K.ReichheldF.F. and SchefterP. (2002). Avoid the four perils of CRM, Harvard Business Review, 80 (2), 101–109.
82.
SabbaghD. (1998). Pathway hits the buffers – The £1bn project to automate benefit payments through the Post Office is in trouble.Computing, July 9, 15.
83.
SammonD. (2001). ERP dreams and sound business rationale. Seventh Americas Conference on Information Systems.
84.
ScheinE.H. (1969, 1988). Process consultation: Its role in organization development. Reading, MA: Addison-Wesley.
85.
ScheinE.H. (1990). Back to the future: Recapturing the OD vision. In MassarikF. (ed.) Advances in organization development (Vol. 1 pp. 13–26). Norwood, NJ: Ablex.
86.
ScheinE.H. (1992). Organizational culture and leadership. Revised edition. San Francisco: Jossey-Bass.
87.
ScheinE.H. (1996). The three cultures of management: The key to organizational learning, Sloan Management Review, 37 (3), 9–20.
88.
ScheinE.H. (1999). Process consultation: Building the helping relationship, Reading, MA: Addison-Wesley.
89.
StammersT. (1997). Business doesn't rate IT staff.Computing, March 27, 10.
90.
VoraM. (1997). A change of title is not enough.Information Strategy, February, 2 (1), 58.
91.
WastellD. and NewmanM. (1996). Information systems development in the ambulance service: A tale of two cities.In Coelho et al (eds)
92.
WorleyC.G.HitchinD.E. and RossW.L. (1996). Integrated strategic change: How OD builds competitive advantage, Reading, MA: Addison Wesley.