Next Article in Journal
Training of Deep Convolutional Neural Networks to Identify Critical Liver Alterations in Histopathology Image Samples
Previous Article in Journal
Immunohistochemical Expression of Wilms’ Tumor 1 Protein in Human Tissues: From Ontogenesis to Neoplastic Tissues
Open AccessArticle

How to Optimize the Implementation of ITIL through a Process Ordering Algorithm

UDIMA, 28400 Collado Villalba, Spain
UNED, 28040 Madrid, Spain
Author to whom correspondence should be addressed.
Appl. Sci. 2020, 10(1), 34;
Received: 26 November 2019 / Revised: 5 December 2019 / Accepted: 11 December 2019 / Published: 19 December 2019
(This article belongs to the Section Computing and Artificial Intelligence)


One of the main points when implementing the Information Technology Infrastructure Library (ITIL) is which order the processes must be implemented. In the systematic literature review (SLR) developed, it is possible to find references about strategies and factors that ease the implementation of the ITIL, static sequences for the processes to be implemented, and recommendations about the first process to implement, but it is rather complicated to find references that explicitly define the order (adapted to a specific company) of the processes to be implemented. Thus, once it is shown that there is no methodology/algorithm providing a sequence of ITIL processes specifically adapted for each company, an algorithm to solve this problem is presented: The algorithm has a deep mathematical basis and returns a sequence of ITIL processes to optimize the efforts during implementation, so the company implementing the ITIL gets the closest to the competitors. The optimization is made considering parameters such as staff, age of the company, IT size, industry, etc. Thus, the sequence proposed is specific for each company. Finally, a comparative of the sequence obtained (from the proposed algorithm) with sequences discovered in the SLR is presented and applied to a real case.
Keywords: ITIL; implementation sequence; process implementation order; optimization; algorithm ITIL; implementation sequence; process implementation order; optimization; algorithm

1. Introduction

There is no doubt about the importance of information resources in organizations. The management of organizations may be very different from one to another but in all cases the quality of IT (information technology) services is directly dependent on common principles, such as adding value, improvement of customer satisfaction and productivity, and/or reducing costs [1].
The main goal of an IT manager is providing the best quality service with fewer resources as possible, and achieving parameters of efficiency, time, cost, etc. To do it, it is possible to adopt and adapt several standards, good practices handbooks, and rules [2,3,4,5,6].
The Information Technology Infrastructure Library (ITIL) is a market standard practices library completely oriented to services and its management, development, and operation [7]. It defines a complete set of processes to offer better IT services from IT companies and IT departments. It could be deduced that these ITIL reference practices are specifically designed for software, technology, or information systems companies, but, in fact, the ITIL can be applied to any organization as it does not depend on its activity. It is just required that the organization is using technology for internal purposes or as services offered to clients. ITIL has been developed to be applied in any type of company [8].
Currently, ITIL is divided in five groups of processes (service strategy, service design, service transition, service operation, service continual improvement) but ITIL does not define a strategy to implement the processes: No order of processes is presented, no dependency on the company where ITIL is implemented, no dependency on the industry, etc. It just includes the processes needed for proper management of IT Services [9].
There is much interest in companies about ITIL implementation [10], and, more specifically, in how it should be implemented: The order of processes to implement, factors that may affect the success of implementation, strategies to follow when implementing, among others. But this interest is just partially solved as there is no a clear methodology or algorithm which provides, to companies, a clear and sequence of processes to implement the ITIL. This lack of criteria (in the order of implementation of the ITIL processes) is one of the reasons that leads to a failure in ITIL implementations. It is clearly addressed in [11]: “Many of the organizations attempt to implement all or many of the ITIL processes at once, that it causes confusion, staff unrest, and poor integration between the processes. Therefore, it is better to select the most important processes for target organization and then schedule their implementation.”; and in [12], a single report explaining why implementations fail: “Traditionally most organization start implementing Incident Management/Problem Management/Change Management/Service Request processes without fixing a configuration management database (CMDB)”.
There are several studies which make approaches around ITIL implementation and how this implementation should be conducted. These studies consider different points of views [13]: Analysis of success factors [14,15,16] (i.e., the factors that most affect the implementation of the ITIL and may have a great influence on the success of the ITIL implementation); the strategy that should be followed to implement ITIL in [10,17,18], that is the overall steps to follow when implementing ITIL; order of how processes should be implemented [9,19,20] (i.e., the sequence of processes should be followed to implement the ITIL properly to maximize success options); considering the characteristics of the organizations [21], which means to consider the size, age, and other specific parameters that may influence the implementation of the ITIL; and finally, an approach considering other specific topics.
Summarizing, authors focus their attention on next issues [13]: 1—Strategy. 2—Success factors. 3—Order of processes. 4—Characteristics of organizations. 5—Specific implementation topics.
Thus, there is not a clear approach to define the strategy to implement the ITIL. It does not matter if we look at the steps, the sequence, the factors, the characteristics of organizations, or if we look at specific issues that may affect the implementation; there is not a clear solution for companies wishing to implement the ITIL. This leads us to one of the main problems to solve [11]: Is it possible to define an algorithm that returns the order of the ITIL processes that a company should implement? In the next sections we will answer this question following the methodology indicated in the coming subsection.


This article presents a study that started with a systematic literature review (SLR) to discover how ITIL processes are ordered by the companies during the implementation phase. Once it was found that no algorithm was used to order processes, we set up the math basis for the optimal ordering algorithm presented in this article. Following this, we built the database (filled up with data from real companies—see Appendix A for the polling details). After that, we deployed the algorithm in a website ( to facilitate its usage on different companies and, finally, we applied the solution proposed to real cases.

2. State of Art

A systematic review of literature to get a deep understanding of the state of art was developed. The references about how to perform a review can be found in [22,23,24,25] applied to different disciplines; however, it is preferable to follow other similar approaches that fit better in engineering disciplines [26]. These references were used to develop the research and analysis of publications. The main question to solve with the SLR is to find methodologies, algorithms, or proposals of sequencing the ITIL processes so companies can implement the ITIL and optimize the efforts. This means that implementation of the ITIL optimizes its position with respect to competitors (in terms of implementation of the ITIL).
A summary of the results of the SLR developed is presented. In order to give an overall idea of the state of art of the ITIL sequences for implementation, next strategies were identified:
  • Non-fixed sequences: These strategies include sequences which are objective dependent. That is, a general strategy or function to organize processes is given. This strategy or function is oriented to a specific objective—maximizing client satisfaction, minimizing implementation time, avoiding deadlocks, etc.—but they, finally, offer the same sequence for every company having the same objective.
  • Static sequences: This second group of strategies define a fixed sequence which is common to every implementation. That is, independently of the size, type, industry—or whatever factor—of the company, the same ITIL sequence is defined. These strategies are usually based on criteria such as polling to experts, dependencies between processes, among others.
  • Implementation examples and critical success factors: The third group of strategies are focused on defining which factor affects the success or the failure of an ITIL implementation. This group also includes those strategies that define rules and methodologies of implementation based on previous cases of real implementations.
These groups of strategies to implement the ITIL are explained in the next paragraphs, based on the literature review developed previously.

2.1. Non-Fixed Sequences

A fuzzy logic-based proposal is presented in [2]. This model is based on the fact that the decision of sequencing is dependent on organizational and technical factors, which are essentially “abstract factors”. It proposes to select the criteria that may influence the sequence through the opinion of experts and fuzzy techniques, to express numerically the ambiguity of such opinions. The main disadvantage of the model stands on the fact that is presented in an absolute manner (it does not consider the type of company, the industry, the size, its resources, and other aspects). A very similar idea was already exposed in [27], where an ITIL process selection model is exposed to be implemented also based on fuzzy logic.
The proposal [28] is oriented to early wins: The implementation proposes, in the first place, the processes that provide “quick wins”, based on satisfaction surveys. Similarly, and depending on the needs, it proposes a strategy where the processes to be implemented are proposed for the medium and long term. The proposal of this author gives a solution for the problem of the order of implementation, but it is easy to verify that the implementation strategy is led by the clients opinions.
The approach of [29] describes an ITIL adoption based on the technology adoption model (TAM). For these authors, the sequence of processes depends on the requisites exhibited by the organization, but the critical processes are known and should have priority over the rest. This idea of dependence on such issues (industry, organization, size, etc.) is also explained in [21]. The authors developed a complete study on the implementation of the ITIL. In this study they show the reasons that make organizations implement the ITIL and define the three definitive elements for the level of implementation of the ITIL: The region or geographical area, the size of the company, and the industry in which it operates.
A compilation work is presented in [13], which is the basis for the sequence proposed: A sequence of processes defined from the validation of a series of variables that may affect the ITIL implementation. These variables take in consideration internal elements of the ITIL: The set of tasks needed to implement an ITIL process, the distribution of data, and the correct flow of information among processes.

2.2. Static Sequences

The reference [20,30] are examples of static sequence where the authors establish a way to measure the relationship among the different processes. These processes, conveniently classified, determine a graph in which cyclical or dependent paths can be found. Thus, the more elements a path has, the more dependencies it contains, and so all the processes involved in that path are compromised: The cycle with the largest number of nodes (that is, processes) or processes is selected.
In [31] the idea of fixing a static sequence is taken again: In this paper, ITIL implementation is organized from the definition of three models:
  • A first model of isolated ITIL processes.
  • Another model that contains the dependencies between ITIL processes.
  • A final model to relate the capacity level of the processes and the maturity level of the organization. One of the main characteristics of this proposal is the combination of concepts of the ITIL and Capablity Maturity Model Integration (CMMI) to propose a sequence.
It could be thought that this proposal describes a dynamic sequence, but in fact the result is a fixed (or very close to be fixed) sequence. The reason is that the second model of the mentioned above, determines which processes should be implemented to implement the next one; so only slight differences in the initial processes can be found. Once these ones have been implemented, the rest of the sequence hardly vary from one organization to other.
A fixed sequence of implementation is also shown in [32]: Although there is not an explicit justification, it shows a sequence that may be used as a reference. It means that companies can use the same sequence, as it is presented as company, geographically, and industry-independent.
In some cases, the objective is not to define explicitly a sequence but, rather, address a starting point, which means defining the first process to implement. This is the case in [9,17,19]—where the proposal has empirical basis supported by market analysis. Once more, the first process to implement the proposed is Incident Management, followed by Service Level Management, and Service Catalog Management.

2.3. Strategies and Critical Success Factors

(a) Critical success factors: Another research area is composed by those authors who try to identify success factors on ITIL implementation: [14,33], where a survey is used to get info about success factors of ITIL implementation in different companies. Another example can be found in [34], where specific success factors are analyzed: Management involvement, organization commitment and effectiveness, and key factors to implement the ITIL.
It is possible to identify also a group of works that provide methodologies and strategies to implement the ITIL [16]: It analyzes the steps to consider when implementing the ITIL (taking in consideration four big companies). From this experience, success factors are defined to a proper implementation of ITIL. It also proposes to start with the Incident Management process, but it does not show any sequence from this starting point.
A different view is proposed in [35], where success factors indicate tools and management as key elements. It is explained how the success does not depend on the sequence but on the software and tools use to a proper management of the implementation task. This point is also addressed by [36], where software tools (mainly BPM) are critical for success.
A compilation work can be found in [18]: An excellent systematic review of success factors and a methodology based on AHP (analytical hierarchical process) are proposed. AHP is a model to evaluate, average, and eliminate inconsistencies among a group of expert opinions.
A vast, extensive work is presented in [34]. In this case a set of success items are presented (mainly they are like those ones in the works indicated before) but compared with more than 160 companies (although—as it is indicated in the publication—it suffers limitations due to geographical issues).
A methodology based on business process change (BPC) is explained in [15]. BPC is used to determine the success factors, although there is nothing about the sequence of processes. A different approach can be found in [37], where failure factors are described: In fact, they are factors that may make the ITIL implementation difficult.
(b) Strategies: Regarding strategies, [8] show how to select processes, but without any sequence. This work proposes a model in which the ITIL processes are classified de-pending on the issues such as infrastructure, resources, actions, and so on. As an alternative, [38] presents a work to define a procedure that may ease the implementation: The rule is based on the level of maturity of the organization for every task. A similar idea is presented in [39], as it also highlights the importance of maturity to decide the processes to be implemented according to objectives, practices, inputs and outputs. Something similar is shown in [40].
In [1], the proposal just indicates the existence of two implementation strategies: One for very small companies and another one for aged companies, but without mentioning anything about the sequence. Finally, a multiagent architecture proposal can be found in [41] (it does not attend for the sequencing problem).

2.4. Non-Fixed Optimal Ordering Algorithm

As it has been shown before, there is no any specific approach offering a methodology, neither an algorithm to define the complete order of processes when implementing the ITIL. This means: (a) No algorithm for non-fixed sequences has been published; and (b) no algorithm for an optimal sequence specifically adapted for each company has been published.
This conclusion leads us to the define the algorithm presented in the next paragraph, where we present how to optimally order the ITIL processes for a specific company depending on: (a) The level of implementation of the ITIL it has already reached; and (b) on the characteristics of the company.

3. Algorithm for Optimal Ordering of ITIL Processes

3.1. Model Basis

The algorithm presented here assumes that a set of companies and its characteristics (size, industry, age, etc.) are available. The objective is to define an algorithm that maximizes the position of a company compared with its competitors in terms of ITIL implementation. The selection of processes to implement depends on the strategic needs of the company and the degree of implementation of every ITIL process compared to the competitors. The algorithm selects the process that maximizes the benefits of ITIL implementation in front of its competitors.
Let Ωe be the set of available companies from which characteristics are known and stored. Usually this set of data is taken from a great poll:
Ω e = { e 1 , e 2 , , e n } .
Let E be any company included in the dataset:
E = e e Ω e .
Let Ωne be the complementary set of Ωe, that is the set constituted by companies that have not been included in the data set:
Ω n e = { e 1 , e 2 , , } e x Ω e .
It will be noted by Esel any company included in this last data set:
E s e l = e x e x Ω e .
Let us denote by Ωp the set of the pITIL processes that can be implemented out of the available data:
Ω p = { p 1 , p 2 , , p p I T I L } .
Let pITIL be the number of ITIL processes that can be implemented, so:
p I T I L = | Ω p | .
Let pi any of the pITIL potential processes that can be implemented and di the assessment of pi process in a particular company, E:
The possible value of di are:
d i ( E ) = { 1   i f   C 1 ( p i ) = T r u e 2   i f   C 2 ( p i ) = T r u e 3   i f   C 3 ( p i ) = T r u e M   i f   C M ( p i ) = T r u e } ,
where Cm(Pi) is a Boolean function that indicates if the pi process satisfies an implementation degree of cm. The possible values for the degrees are in the interval [1..M], so 1 represents the worst option and M represents the best option. That is:
C m :   Ω p B o o l e a n   |   C m ( p i ) =   { T r u e , i f   p i   s a t i s f i e s   c m F a l s e , i f   p i   s a t i s f i e s   ¬ c m } ,
For example, the c1 condition could mean that the process is not implemented, neither will it be in the long term; in that case C1(pi) = True would indicate that pi is not implemented, neither will it be implemented in the long term in company E; in such case di(E) = 1.
It should be noticed that {1...M} represents the values given to the different degrees of implementation that a pi process may have in company E.
Let Ωv be the set of the v parameters that define the characteristics of every company, which are identified by {v1, v2, …, vv}. Such parameters could be the type of activity, the age, the number of employees, the geographical area where it operates, etc.,
Ω v = { v 1 , v 2 , , v v }   |   v = | Ω v | .
Following this, let us define the domain of each parameter that belongs to Ωv:
Ω v k = { v k 1 , v k 2 , , v kn k }   |   k ( 1 . . v ) n k = | Ω v k | ,
where nk represents the number of possible values for the parameter vk.
Next, let us define every v functions {V1, V2, …, Vv} which assign a value vij to the parameter vi for the company E:
V i : Ω e Ω v i   |   V i ( E ) = v i j     v i j Ω v i     i ( 1 . . v ) .
In such case, the v vector of parameters which define the characteristics of a company are given by:
V ( E ) = { V 1 ( E ) V 2 ( E ) V v ( E ) } = { v 1 t 1 v 2 t 2 v v t v }   where   v it i Ω v i     t k ( 1 . . | Ω v k | ) .
Next, si1j is defined as the average of the assessment of the pi process for the companies that satisfy v1 = v1k:
s i 1 k = d ¯ i ( e m ) e m   |   V 1 ( e m ) = v 1 k k ( 1 . . | Ω v 1 | ) .
In a general way, the average of the assessment of the pi process for all companies which satisfy vj = vjk can be denoted by sijk:
s i j k = d ¯ i ( e l ) e l   |   V j ( e l ) = v jk   |   i ( 1 . . p ITIL ) j ( 1 . . v ) k ( 1 . . v j ) .
Or, expressed in a more formal way:
s i j k = l = 1 n e d i ( e l ) n e   |   V j ( e e ) = v j k i ( 1 . . p ITIL ) n e = | Ω V j ( e e ) = v j k | .
This means that the average of the assessments di for the pi process for every company ee whose parameter Vj satisfies Vj(ee) = vjk. The ordinality of the set of companies that satisfy such condition is given by:
n e = | Ω V j ( e e ) = v j k | .
At this point, it is possible to show the algorithm that allows any company to decide which process should be first implemented.
Let us define Esel as any company not included in the set Ω e :
E sel = e x   |   e x Ω e .

3.2. Criteria for Establishing the Sequence

In order to decide which process should be first implemented, it is necessary to define a parameter containing information about the implementation of an ITIL process in other companies with similar characteristics. To define it, and taking in consideration the definitions presented in previous paragraphs, the next parameters are needed; where Sijk is referred to the set of available set of companies in the database and Di is specifically referred to the company Esel:
S i j k = ( M s i j k ) i ( 1 . . p ITIL ) j ( 1 . . v ) k ( 1 . . v j ) D i = ( M d i ) i ( 1 . . p ITIL ) .
In this expression, M represents the maximum value that the implementation of an ITIL process pi can take. This M value represents a complete implementation of the pi process or a very short-term implementation.
It can be seen how Sijk represents, for a specific pi process, the distance between the maximum value M and the average of the values of implementation for that particular process in companies with the same characteristics vjk as Esel. It can be also seen how Di represents the distance between the maximum value M from the response of the company Esel.
It is necessary to define an indicator or parameter to help us to decide the best process to be implemented next. This indicator should take high values when the relative position (in terms of implementation of a process) is better than the reference companies denoted by V(Esel). This indicator should also take low values when the company is in a worse position than similar companies with characteristics V(Esel).
Let r be the indicator “relative position” defined as follows:
r = S α 2 S β 2 S γ 2 S δ 2 D 2 .
This indicator can be particularized for a particular process pi and for all companies with the same characteristics V(Esel):
r i = j = 1 v S i j t j 2 D i 2   |   V j ( E s e l ) = v j t j ,
where ri represents the value of the r indicator for the company Esel and for the process pi.
This expression calculates ri from the S2 value for each group of companies that satisfy the condition of having the same characteristics as Esel: Low values of Di indicate that the process pi is implemented or it will be soon in the company Esel; on the other hand, high values of Di indicate that process is not implemented, neither will it be in the short term. At the same time, high values for Sijtj address that the pi process is not implemented in the companies with the same characteristics v j t j , while low values show this process is implemented in companies with same characteristics, but it is not in Esel.
As a consequence, if the pi process is implemented in similar companies but it is not in the company Esel (that is, Esel position is worse than competitors), this leads to a really small value for r, compared to the maximum value it could take; it can be also shown that if a company has the process pi implemented but similar companies do not (that is, the relative position of Esel is better than competitors), then r will take a high value. Thus we can conclude that parameter r is a measurement of the relative position of a company for a specific process pi compared to similar companies. Anyway, the value of r goes from 0 to 1.
Thus, we can formalize ri as the relative positioning indicator and Ri as the function to evaluate ri:
R i : Ω ne       |   R i ( e x ) = r i     +   e x     Ω ne .
Thus, Ri represents the function that evaluates the relative positioning ri if a company ex for the process pi compared to similar companies.
Once this indicator is defined, it is possible to define the selection criteria for the first process to be implemented:
p o p t = p   |   r p = m í n ( r i ) i = { 1 , 2 , . . p ITIL } .
This expression means that the best process and the one that should be first implemented, that is, the one that will most improve the rank of the company (in terms of ITIL implementation) compared to the competitors, is the one with the lowest value for rp, that is, the one that has the lowest relative positioning.
The criteria shown previously needs a small correction: Due to the fact that relative positioning r has taken into account the situation of the process in the company itself, every process that is already implemented should be excluded; that is, the processes with Di = 0. This obliges the exclusion of every process that has been already implemented and review only processes with Di ≠ 0.
P o p t = p   |   r p = m í n ( r i ) i = { 1 , 2 , . . p ITIL }   |   D i 0 .
Thus, if we select iteratively the Popt process (of course, on every iteration this process will be different as Popt process has already been implemented in the previous iteration and so, dismissed as selectable), we get a sequence of processes to implement that optimizes the degree of implementation compared to the competitors, for the criteria defined (age, size, etc.).

4. Results: Comparative of Sequences in a Real Case

As mentioned before, there is not a generic methodology to sequence ITIL processes which takes into consideration the parameters of each company. A solution for this has been developed and it lays on data gathered from different companies. This information allows a candidate sequence to be proposed for a company depending on the size, industry, age, and other parameters. Of course, this solution generates a sequence for each company that aims to implement ITIL.
It is necessary to compare the results of such optimal implementation with the sequences obtained in the literature review. The objective of this comparative is to determine if the sequence is significantly different from the ones proposed by different authors. The proposals of sequence selected are S1: [9], S2: [13], S3: [32], S4: [21], S5: [2], and S6: [31], as these proposals include a greater number of processes.
To determine if the proposed sequence and the reference sequence are independent, Spearman contrast and Kendall contrast were used. In both cases the null hypothesis is that both sequences (the reference one and the proposed one) are independent; and the alternative hypothesis is that both sequences are related (that is, there is not a significant difference). The level of confidence used was α = 0.1.
For every real company, an optimal sequence is obtained and, so, the comparation with the referenced sequences may lead to one of next results: The optimal sequence is significantly different from the reference sequence or the optimal sequence is not significantly different from the reference sequence. In addition, even in this second case it may occur that selected processes for implementation are the same, but they are selected in a smoothly different order (not statistically different).
As an example, a real, small, and young IT consultancy company located at Madrid (Spain) with less than nine employees was selected for testing. The algorithm is required to propose an optimal sequence considering five criteria (staff, IT employees, company age, industry, area). The application of the algorithm requires a database with data from other companies and make calculations with them (more information about this issue in Appendix A). The order of processes obtained is (just the 10 first processes are shown):
1—continuous improvement; 2—management of catalogue; 3—incident management; 4—validation and testing; 5—availability management; 6— service portfolio management; 7—financial management; 8—configuration management; 9—transition management; 10—access management.
Results of the comparative with other sequences are shown in Table 1:
From Table 1, it is relevant to conclude that the optimal proposed sequence is significantly different from the first five reference sequences and, at the same time, is optimized for the criteria given by the company. For the sequence S6, the optimal sequence has a ρ value out of the limits (that is, we cannot accept the null hypothesis), although the value is quite close to the limit; nevertheless, for the Kendal contrast the τ value is clearly inside the limits (which allows us to accept the null hypothesis).
Let us remember that the optimal sequence selects processes iteratively, so the global degree of the ITIL implementation on a company is maximized when compared with similar companies in terms of size, IT size, age, industry, etc. This optimal sequence is significantly different from the published sequences by different authors.
The significance of the experiment is based on the fact that companies obtain a sequence of processes to implement ITIL at very low cost (no experts are needed), defining the criteria for optimization and considering the degree of implementation already reached at the moment.

5. Discussion

The proposed algorithm offers a sequence of ITIL processes that in most cases is different from the known existing proposals. This approach has benefits, listed below:
  • The proposed sequence is obtained from a mathematical model, so it does not depend on the opinion of experts—as most of the proposals in the literature review do—neither on subjective issues. This is a valuable point, because not all companies (especially small companies) can afford to pay a set of experts to decide how to implement processes of the ITIL. This is also a valuable issue as it avoids ambiguity and subjective opinions and leads to a repeatable process for the estimation of the best sequence for a company.
  • The proposed sequence is obtained so the order of processes proposed maximizes the efforts of implementation: It gets the company the closest to competitors, if the implementation of ITIL processes in that company is far from the average, and it gets the company to a better position even if it is over the average. Due to the calculation of the relative position factor and its optimization, the process selected in every iteration is the one that optimizes the positioning in terms of ITIL implementation.
  • The company may select the criteria to optimize efforts of implementation: size, age, region, etc. Thus, every company will obtain different sequences especially set for each one. As no approach defining a sequence that depends on characteristics selectable by the company has been found, this functionality represents an advantage; companies can decide what are the most important factors when implementing the ITIL and can obtain a sequence that best fits its needs.
  • The solution proposed will get more accurate as the database is filled with more and more company data. The database used with the algorithm has information about five parameters of each company, as well as the value of the degree of implementation of every ITIL process: As more data it added, a better solution is produced from the algorithm, as more information is known about what other companies are doing (about ITIL implementation)
  • Comparatively, this solution may be (and really it is) implemented in a software platform which is easier and cheaper than considering experts, as some approaches do. As it has been said before, the algorithm has a mathematical basis which simplifies its implementation in a software program.
  • Due to fact that the solution proposed is specific for each company, a higher satisfaction of clients is expected (companies implementing the ITIL).
  • Although it is not a benefit of the algorithm itself, the software platform used offers a comparative with other proposals. Based on this comparison, the statistics tests show how different this proposal is from other approaches.
On the other hand, the algorithm needs a database with characteristics of companies and the degree of implementation of every ITIL process, so the geographic limitation on its use could be considered a disadvantage. In the real case analyzed, the data for the database was obtained from Spanish companies. Anyway, the algorithm is valid once a data set for that specific region is available. Just an update of data makes the algorithm useful in other regions.

6. Conclusions

The selection of ITIL processes to be implemented is quite important in order for it to succeed. The literature about how to implement the ITIL is huge, but there is no a common approach about the selection neither the order of processes. The main approaches are: (a) A fixed sequence independent of the characteristics of the company; (b) a non-fixed sequence, in these cases there is a great influence of internal or experts opinions about the order of processes; and (c) to pay attention to factors that may help to succeed but without explicitly defining a sequence.
After the literature review, a model for selection was presented, which was based on selecting the process that places the company the nearest to competitors, taking in consideration several factors as size, industry, market, IT size, etc. This proposal is referred to as optimal as it minimizes the distance between the company (in terms of ITIL implementation) and the rest of similar companies. The main advantage of this selection algorithm is that it allows the implementation to be optimized, taking into consideration the different characteristics or parameters of the company. In the literature review, no algorithm was found that allows an implementation sequence to be obtained in such a way.
Although extending the testing of the algorithm to more and more companies is needed, the initial results show that this different algorithm really produces a different sequence of processes. The initial comparison with other techniques shows that sequences are statistically different, and the companies obtain the optimal sequence to get the closest to competitors, as the selection algorithm is designed to do so.
Of course, the algorithm needs a database of companies with its characteristics and the degree of implementation for every ITIL process, as that is the basis to optimize the sequence proposed. Anyway, the database value improves with every company that is introduced, as that results in a better proposal of sequence.
For the small IT consultancy company examined, the results show that the new optimal sequence is significantly different from the existing ones. Future works are oriented to test the algorithm on more companies to get an idea of the overall discrepancies between the proposed sequence and the reference approaches.

Author Contributions

Conceptualization, J.L.R.; methodology, J.L.R.; software, J.L.R.; validation, M.A.; formal analysis, J.L.R.; investigation, J.L.R. and M.A.; writing—original draft preparation, J.L.R.; writing—review and editing, M.A. All authors have read and agreed to the published version of the manuscript.


This research received no external funding.

Conflicts of Interest

The authors declare no conflicts of interest.

Appendix A

The data for the database as obtained from a poll. Table A1 shows the characteristics of this polling:
Table A1. Description of the polling.
Table A1. Description of the polling.
UniverseCompanies with more than one employee
Type of pollingWeb form
Minimum to be significant64
Confidence level90%
Company selectionRandom


  1. Mitev, Y.; Kirilov, L. Using IT Management Processes for Achieving Better Efficiency in the IT Service. In Proceedings of the ICEST 2014, Niš, Serbia, 25–27 June 2014; Volume 1, pp. 247–250, ISBN 978-86-6125-108-5. Available online: (accessed on 31 May 2018).
  2. Zare, A.; Mansouri, T.; Mehrabioun, M. Supporting the module sequencing decision in ITIL solution implementation: An application of the fuzzy TOPSIS approach. Int. J. Inf. Technol. Syst. Approach 2014, 7, 41–60. [Google Scholar] [CrossRef]
  3. HP. HP IT Service Management (ITSM). Transforming IT Organizations into Service Providers. 2003. Available online: Ftp:// (accessed on 31 May 2018).
  4. Bahsani, S.; Himi, A.; Moubtakir, H.; Semma, A. Towards a poolimg of ITIL v3 and COBIT. Int. J. Comput. Sci. Issues 2011, 8, 185. [Google Scholar]
  5. Pérez, D.H. De la Administración al Gobierno de TI. 2008. Available online: (accessed on 31 May 2018).
  6. Hesch, J. COBIT in relation to other international standars. Inf. Syst. Control J. 2004, 4, 37–40. [Google Scholar]
  7. Van Bon, J.; de Jong, A.; Kolthof, A.; Pieper, M.; Tjassing, R.; van der Veen, A.; Verheijen, T. Gestión de Servicios TI Basado en ITIL; Haren, V., Ed.; The Netherlands, 2016. [Google Scholar]
  8. Fry, M. ITIL Lite: A Road Map to Full or Partial ITIL Implementation; The Stationery Office: Norwich, UK, 2010; ISBN 0113312121 9780113312122. [Google Scholar]
  9. Lema, L.; Calvo-Manzano, J.A.; Colomo-Palacios, R.; Arcilla, M. ITIL in small to medium sized enterprises software companies: Towards an implementarion sequence. J. Softw. Evol. Process 2015, 27, 528–538. [Google Scholar] [CrossRef]
  10. Cater-Steel, P.; Carol, A. Justifications, strategies and critical success factors in successful ITIL implementations in US and Australian companies: An exploratory study. Inf. Syst. Manag. 2009, 26, 164–175. [Google Scholar]
  11. Sharifi, M.; Ayat, M.; Rahman, A.; Sahibuddin, S. Lessons Learned in ITIL Implementation Failure. In Proceedings of the 2008 International Symposium on Information Technology, Kuala Lumpur, Malaysia, 26–28 August 2008; Volume 1, pp. 1–4. [Google Scholar] [CrossRef]
  12. Website: Top 10 Reasons Why do ITSM Implementation Fails. Available online: (accessed on 31 July 2019).
  13. Miller, A.C. Implementation Priority of the ITIL Framework Based on a Process Sequencing Model. Ph.D. Thesis, The George Washington University, Washington, DC, USA, 2017. [Google Scholar]
  14. Cater-Steel, A.; Tan, W.G. Implementation of IT Infrastructure Library (ITIL) in Australia: Progress and Success Factors. In Proceedings of the IT Governance International Conference, Auckland, New Zealand, 14–16 November 2005. [Google Scholar]
  15. Pedersen, K.; Kræmmergaard, P.; Lynge, B.C.; Schou, C.D. ITIL implementation: Critical success factors a comparative case study using the BPC framework. J. Inf. Technol. Case Appl. Res. 2010, 12, 11–35. [Google Scholar] [CrossRef]
  16. Khosravi, H.; Wang, J. How to Implement ITIL Successfully?: What Steps are Necessary to Implement ITIL What Factors are Critical within Implementation Process; LAP Lambert Academic Publishing: Saarbrucken, Germany, 24 October 2011; ISBN 978-3-8454-7646-9. [Google Scholar]
  17. Masarat, A.; Mohammad, S.; Shamsul, S.; Sulaimi, I. Adoption Factors and Implementation Steps of ITSM in the Target. In Proceedings of the 2009 Third Asia International Conference on Modelling & Simulation, Bali, Indonesia, 25–29 May 2009; pp. 369–374. [Google Scholar]
  18. Ahmad, N.; Shamsudin, Z.M. Systematic Approach to Successful Implementation of ITIL. In Proceedings of the 1st International Conference on Information Technology and Quantitative Management (ITQM), Suzhou, China, 16 May 2013. [Google Scholar]
  19. Calvo, J.A.; Lema, L.; Arcilla, M.; Rubio, J.L. How small and medium enterprises can begin their implementation of ITIL? Rev. Fac. Ing. Univ. Antioq. 2015, 77, 127–136. [Google Scholar] [CrossRef]
  20. Arcilla, M.; Calvo, J.; Cuevas, G.; Gómez, G.; Ruiz, E.; San Feliu, T. A Solution for Establishing the Information Technology Service Management Processes Implementation Sequence; O’Connor, R.V., Baddoo, N., Smolander, K., Messnarz, R., Eds.; Software Process Improvement; EuroSPI 2008; Communications in Computer and Information; Springer: Berlin/Heidelberg, Germany, 2008; Volume 16. [Google Scholar]
  21. Marrone, M.; Gacenga, F.; Cater-Steel, A.; Kolbe, L. IT Service Management: A Cross-national Study of ITIL Adoption. Commun. Assoc. Inf. Syst. 2014, 34, 49. [Google Scholar] [CrossRef]
  22. Centre for Reviews and Dissemination, University of York. Systematic Reviews: CRD’s Guidance for Undertaking Reviews in Health Care; Centre for Reviews and Dissemination: York, UK, 2009; Available online: (accessed on 31 July 2019).
  23. Brereton, P.; Kitchenham, A.; Budgen, D.; Turner, M.; Khalil, M. Lessons from applying the systematic literature review process within the software engineering domain. J. Syst. Softw. 2007, 80, 571–583. [Google Scholar] [CrossRef]
  24. Kitchenham, B.; Charters, S. Guidelines for Performing Systematic Literature Reviews in Software Engineering; Version 2.3; EBSE Technical Report EBSE-2007-01; Keele University: Newcastle-under-Lyme, UK; University of Durham: Durham, UK, 2007. [Google Scholar]
  25. Petticrew, M.; Roberts, H. Systematic Reviews in the Social Sciences: A Practical Guide; Blackwell Pub: Malden, MA, USA, 2005. [Google Scholar]
  26. Stapic, S.; López, E.G.; Cabot, A.G.; Ortega, M.; Strahonja, L.V. Performing Systematic Literature Review in Software Engineering. In Proceedings of the Central European Conference Information and Intelligent Systems (CECIIS’ 12), Varazdin, Croatia, 19–21 September 2012; pp. 441–447. [Google Scholar]
  27. Zarrazvand, H.; Shojafar, M. The Use of Fuzzy Cognitive Maps in Analyzing and Implementation of ITIL Processes. arXiv 2012, arXiv:1206.2297. [Google Scholar]
  28. Menken, I. ITIL V3 Implementation Quick Guide–The Art of Stress-Free IT Service Management; Emereo Pty Ltd.: London, UK, 2009. [Google Scholar]
  29. Mehravani, S.; Haghighinasan, M.; Hajjiheydari, N. ITIL adoption model based on TAM. In 2011 International Conference on Social Science and Humanity; IACSIT Press: Singapore, 2011; IPEDR; Volume 5. [Google Scholar]
  30. Arcilla, M.; Ruiz, E.; Cerrada, C.; Gómez, G.; Calvo-Manzano, J.A.; San Feliu, T.; Sánchez, A. Una propuesta organizativa de los procesos de SD y SS en ITIL. REICIS. Rev. Española Innovación Calid. Ing. Softw. 2007, 3, 6–20. [Google Scholar]
  31. Pastuszak, J.; Czarnecki, A.; Orlowski, C. Ontologically Aided Rule Model for the Implementation of ITIL Processes. In Advances in Knowledge-Based and Intelligent Information and Engineering Systems; Graña, M., Toro, C., Posada, J., Howlett, R.J., Jain, L.C., Eds.; IOS Press: Amsterdam, The Netherlands; pp. 1428–1438.
  32. Lucio-Nieto, T.; Colomo-Palacios, R.; Soto-Acosta, P.; Popa, S.; Amescua-Seco, A. Implementing an IT service information management framework: The case of COTEMAR. Int. J. Inf. Manag. 2012, 32, 589–594. [Google Scholar] [CrossRef]
  33. Melendez, K.; Davila, A.; Pessoa, M. Information technology service management models applied to medium and small organizations: A systematic literature review. Comput. Stand. Interfaces 2016, 47, 120–127. [Google Scholar] [CrossRef]
  34. Iden, J.; Eikebrokk, T.R. The impact of senior management involvement, organisational commitment and group efficacy on ITIL implementation benefits. Inf. Syst. E-Bus. Manag. 2015, 13, 527–552. [Google Scholar] [CrossRef]
  35. Roar, T.; Iden, J. ITIL Implementation: The Role of ITIL Software and Project Quality. In Proceedings of the 2012 23rd International Workshop on Database and Expert Systems Applications, Vienna, Austria, 3–7 September 2012; IEEE Computer Society: Washington, DC, USA, 2012; pp. 60–64. [Google Scholar] [CrossRef]
  36. Mahy, Y.; Ouzzif, M.; Bouragba, K. Supporting ITIL Processes Implementation Using Business Process Management Systems. In Proceedings of the Third International Conference on Systems of Collaboration (SysCo), Casablanca, Morocco, 28–29 November 2016; pp. 1–4. [Google Scholar] [CrossRef]
  37. Shang, S.; Lin, S. Barriers to implementing ITIL-a multi-case study on the service-based industry. Contemp. Manag. Res. 2010, 6, 53. [Google Scholar] [CrossRef]
  38. Sousa, R.; Mira, M. A Maturity Model for Implementing ITIL v3. In Proceedings of the 2010 IEEE 6th World Congress on Services, Miami, FL, USA, 5–10 July 2010. [Google Scholar]
  39. Binders, Z.; Romanovs, A. ITIL self-assessment approach for small and medium agencies. Inf. Tecnol. Manag. Sci. 2014, 17, 138–143, Ed De Gruiter. [Google Scholar] [CrossRef]
  40. Ahmad, N.; Noha, T.A.; Qutaifan, F.; Alhilali, A. Technology adoption model and a road map to successful implementation of ITIL. J. Enterp. Inf. Manag. 2013, 26, 553–576. [Google Scholar] [CrossRef]
  41. El Yamami, A.; Mansouri, K.; Qbadou, M. Toward a New Multi-Agents Architecture for the Adoption of ITIL Framework by Small and Medium-Sized Enterprises. In Proceedings of the 4th IEEE International Colloquium on Information Science and Technology (CiSt), Tangier, Morocco, 24–26 October 2016. [Google Scholar]
Table 1. Comparative proposed sequence–reference sequence.
Table 1. Comparative proposed sequence–reference sequence.
Reference SequenceSpearman Contrast
(|ρ Value|/|Limit Value|)
Spearman Contrast
(|ρ Value|/|Limit Value|)
Back to TopTop