Lessons Learnt from the Improvement of Customer Support Processes: A Case Study on Incident Management

IT Infrastructure Library (ITIL) is the most widely used IT service management framework that provides guidelines how to create, manage and support IT services. Service support processes, such as incident management and problem management, are among the first ITIL processes that organizations start to implement. However, several challenges may exist in the process implementation. The research question of this study is: which issues are important in establishing an ITIL-based incident management process? The main contribution of this paper is to present lessons learnt from an ITIL-based process improvement project that focused on establishing an incident management process in an IS department of a university hospital. Our results show that key issues in implementing incident management are to 1) define the basic concepts of incident management with concrete examples and 2) define process interfaces between incident management and other support processes.

[1]  Chi Fai Cheung,et al.  A multi-perspective knowledge-based system for customer service management , 2003, Expert Syst. Appl..

[2]  Stuart Anderson,et al.  Requirements Evolution from Process to Product Oriented Management , 2001, PROFES.

[3]  Akira Fukuda,et al.  Introducing fault tree analysis into product line software engineering for exception handling feature exploitation , 2007, ICSE 2007.

[4]  Kristi Evans,et al.  Building an IT help desk: from zero to hero , 2005, SIGUCCS '05.

[5]  David N. Card,et al.  Learning from Our Mistakes with Defect Causal Analysis , 1999, IEEE Softw..

[6]  Hans van Vliet,et al.  Software maintenance from a service perspective , 2000 .

[7]  Robert J. Howlett,et al.  A Web-Based Customer Support Knowledge Base System , 2008, KES.

[8]  R. Yin Case Study Research: Design and Methods , 1984 .

[9]  Lakhmi C. Jain,et al.  Knowledge-Based Intelligent Information and Engineering Systems , 2004, Lecture Notes in Computer Science.

[10]  Alain Abran,et al.  Software Maintenance Maturity Model (SMmm): the software maintenance process model , 2005, J. Softw. Maintenance Res. Pract..

[11]  Watts S. Humphrey A Personal Commitment to Software Quality , 1995, ESEC.

[12]  Jay Graham,et al.  Knowledge integration with a 24-hour help desk , 2000, SIGUCCS '00.

[13]  Anne L. Jackson,et al.  Documentation meets a knowledge base: blurring the distinction between writing and consulting (a case study) , 1998, SIGDOC '98.

[14]  M. Kajko-Mattsson,et al.  Corrective maintenance maturity model (CM/sup 3/): maintainer's education and training , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[15]  Anne Miller Integrating human factors in customer support systems development using a multi-level organisational approach , 1996, CHI '96.

[16]  K. Eisenhardt Building theories from case study research , 1989, STUDI ORGANIZZATIVI.

[17]  Keith H. Bennett,et al.  Software maintenance and evolution: a roadmap , 2000, ICSE '00.

[18]  E. B. Swanson,et al.  Software maintenance management , 1980 .

[19]  William A. Florac Software Quality Measurement: A Framework for Counting Problems and Defects , 1992 .

[20]  Hans van Vliet,et al.  Towards Mature IT Services , 1998 .

[21]  Ronald E. Giachetti,et al.  Knowledge management-centric help desk: specification and performance evaluation , 2005, Decis. Support Syst..

[22]  João Caldeira,et al.  Influential Factors on Incident Management: Lessons Learned from a Large Sample of Products in Operation , 2008, PROFES.