Yohannes Mulushoa Girma
Yohannes Mulushoa Girma
By: YohannesMulushoaGirma
August, 2019
Addis Ababa, Ethiopia
School of Commerce Distance Graduate Program
Project Management /MAPM/Unit
By: YohannesMulushoaGirma
(GSD/1940/09)
By: YohannesMulushoaGirma
Approved by:
I, Yohannes Mulushoa Girma, declare that the study entitled “Assessment of Management Roles
Effectiveness for Enterprise Resource Planning (ERP) System Implementation ProjectSuccess:
The Case of Ethiopian Electric Utility (EEU) ERP Project” is the result of my own effort and
study that all sources of materials used for the study have been acknowledged. I have conducted
the study independently with the guidance and comments of the research advisor. This study has
not been submitted for any degree in any university. It is conducted for the partial fulfillment of
the Master of Arts Degree in Project Management.
____________________________________ _______________________________
i
LETTER OF CERTIFICATION
This is to certify that Yohannes Mulushoa Girma has conducted this project work entitled
“Assessment of Management Roles Effectiveness for Enterprise Resource Planning (ERP)
System Implementation Project Success: The Case of Ethiopian Electric Utility (EEU) ERP
Project” is under my supervision.
This project work is original and suitable for the submission in partial fulfillment of the
requirement for the award of Master of Arts Degree in Project Management.
ii
ACKNOWLEDGEMENT
First of all, I would like to thank the Almighty God who gave me strength and encouragement to
complete the courses of this study. I am grateful to my family who had given a lot of
encouragement and motivation to complete my study. I would also like to express my sincere
appreciation to my advisor Dr. Abdurezak Mohammed for the guidance, assistance and constant
support throughout this study. I also want to acknowledge all organizations and individuals of
the Ethiopian Electric Utility who gave me data and materials. Last but not least, to those who
had contributed assistance, either directly or indirectly, yet their names are not cited here, they
deserve my greatest gratitude.
iii
Table of Contents
DECLARATION ......................................................................................................................................... i
LETTER OF CERTIFICATION................................................................................................................. ii
ACKNOWLEDGEMENT ..........................................................................................................................iii
Table of Contents ........................................................................................................................................iv
Lists of Tables ........................................................................................................................................... vii
Lists of Figures ......................................................................................................................................... viii
Lists of Acronyms....................................................................................................................................... ix
Abstract ....................................................................................................................................................x
Chapter One: Introduction .......................................................................................................................... 1
1.1. Background of the Study ............................................................................................................. 1
1.2. Background of the EEU's ERP Implementation Project .............................................................. 1
1.3. Statement of the Problem ............................................................................................................ 2
1.4. Objectives of the Study ............................................................................................................... 3
1.5. Significance of the Study ............................................................................................................ 3
1.6. Scope of the Study ...................................................................................................................... 4
1.7. Limitations of the Study .............................................................................................................. 4
1.8. Organization of the Paper ............................................................................................................ 4
Chapter Two: Review of Related Literatures .............................................................................................. 5
2.1. ERP Implementation ................................................................................................................... 5
2.2. ERP Implementation Benefits ..................................................................................................... 6
2.3. ERP Implementation Challenges and Critical Success Factors ................................................... 7
2.4. Models to Evaluate ERP Implementation.................................................................................... 9
2.5. The conceptual framework of the study .................................................................................... 10
2.5.1. The Top Management Role ............................................................................................... 12
2.5.2. The Technology Management Role................................................................................... 13
2.5.3. The Process Management Role ......................................................................................... 14
2.5.4. The Change Management Role ......................................................................................... 15
2.5.5. The Project Management Role .......................................................................................... 16
2.6. Dependent and Independent Variables of the Study .................................................................. 19
iv
2.6.1. Dependent Variable: ERP Implementation Success .......................................................... 19
2.6.2. Independent Variables: Pillars of Successful ERP Implementations (Roles)..................... 19
Chapter Three: Research Methodology..................................................................................................... 20
3.1. Research Strategy ...................................................................................................................... 20
3.2. Research Design........................................................................................................................ 20
3.3. Sampling Techniques and Sample Size ..................................................................................... 20
3.4. Data Collection Methods and Approaches ................................................................................ 22
3.5. Method of Data Analysis........................................................................................................... 22
Chapter Four: Data Presentation, Analysis and Interpretation .................................................................. 23
4.1. Demographic Information of End Users Respondents .............................................................. 23
4.2. Descriptive Statistics ................................................................................................................. 24
4.2.1. The Top Management Role ............................................................................................... 24
4.2.2. The Technology Management Role................................................................................... 25
4.2.3. The Process Management Role ......................................................................................... 25
4.2.4. The Change Management Role ......................................................................................... 26
4.2.5. The Project Management Role .......................................................................................... 27
4.2.6. ERP Implementation Success ............................................................................................ 27
4.3. Reliability Test .......................................................................................................................... 28
4.4. Validity Test ............................................................................................................................. 29
4.5. Correlation Analysis ................................................................................................................. 29
4.6. Qualitative Analysis .................................................................................................................. 32
4.6.1. Top Management Role ...................................................................................................... 32
4.6.2. Technology Management Role.......................................................................................... 32
4.6.3. Process Management Role ................................................................................................ 32
4.6.4. Change Management Role ................................................................................................ 33
4.6.5. Project Management Role ................................................................................................. 33
4.6.6. ERP Implementation Success ............................................................................................ 33
4.6.7. Interview Responses.......................................................................................................... 33
4.7. Discussion on the Findings ....................................................................................................... 34
Chapter Five: Conclusion and Recommendation ...................................................................................... 37
5.1. Conclusion ................................................................................................................................ 37
5.2. Recommendation ...................................................................................................................... 37
v
References ................................................................................................................................................ 39
Annex 1 – Questionnaire for End Users .................................................................................................... 44
Annex 2 – Questionnaire for Package Leads and Core Team Members ................................................... 48
vi
Lists of Tables
vii
Lists of Figures
viii
Lists of Acronyms
ix
Abstract
This case study is conducted in Ethiopian Electric Utility (EEU) to assess Enterprise Resource
Planning (ERP)implementationsuccessbased on Management Roles effectiveness. Thus the
study;by adapting previous research work that tried to group related Critical Success Factors
(CSFs) into five Management Roles, developed a research framework that associate the
management roleseffectiveness with the ERP implementation success; and also by using various
data collection methods (qualitative and quantitative) in combination with purposive sampling
techniqueto select 167 samples and using the opinions of the project managers, core team
members, end users and consultants/implementation partners assessed the implementation
success, test the relationship and draw explanation.
The result ofthe studyshows that; with the established criteria EEU's ERP implementation
performance is under average;found that the Top Management, Technology Management,
Process Management, Change Management and Project Management Roles have a strong and
positive relationship with ERP implementation success; andall the management roles have a
respectable amount of variance to explain the ERP Implementation Success. Additionally, in
order to exploit the full potential from ERP, more efforts to be practiced to improve the
effectiveness of the five management rolesand further research in the five management roles
areas are recommendedfor the case of EEU.
x
Chapter One: Introduction
These days ERP has become one of the most important developments in the corporate use of
information technology as a strategic tool, which equips the enterprise with the necessary
capabilities to integrate and synchronize the isolated functions into streamlined business
processes (Kanhaiya, 2006). Although ERP implementation is growing very fast and many
companies taking initiatives to implement ERP, it is expensive and not a magic tool which will
transform everything overnight. ERP systems, when implemented successfully, bring significant
benefits. However, successful implementation is a long journey towards enterprise excellence
that many issues need to be addressed to achieve the expected results from the implementation.
Additionally,the successful implementation rate is low and manyfirms that have gained some
benefits from ERP haveyet to exploit the full potential of ERP in theirorganizations (Zhang et al.,
2003).
1
The main reasons for implementing the ERP system in EEU were to facilitate customer service;
to increase efficiency, effectiveness, performance and productivity; to integrate information in
business processes and practices; to decrease burdens for managers and employees; to reduce
cost; to use better technology; and timely problem solving. Because, the legacy system was
facing many challenges and pains resulted from not having ERP system. The draw backs in the
legacy system were: Using lots of different software for different processes, so that, easily access
to information about the business was difficult; Accounting takes longer that sales and the
customers experience are suffering; Business operation are not smoothly facilitated due to
complex and time-consuming ICT; and Organizational resources not managed efficiently and
effectively.
The project will cover all business units and locations of EEU all over the country and the
implementation of the ERP system is divided into two go live and roll out phases (EEP, 2015).
The first phase covers EEU's all business areas located at Addis Ababa; that is, Head quarter, 7
different locations and 75 customer service centers. In the second phase, the go live and rollout
will cover all regional business locations outside Addis Ababa.
However, most of the studies carried on CSFs areas lack theoretical basis that successfully link
the CSFs toimplementation outcomes of any kind (Otieno, 2010). Besides, there is no consensus
on CSFs owing to difference in context between implementing organizations (Leopoldo &
Otieno, 2005). Thus, Frimpon (2012) recommended that, it is better to bringsome structure into
2
the process by placing the possibly conflicting CSFs into separate groups, i.e., top management,
technology management, process management, change management, and project management
role groups where they maytogether help achieve the sub-objectives of the main ERP objective
of a successful implementation.
Although the first phase of EEU's ERP implementation project is go lived, the system is not
stabilized as expected. It is essential to identify the CSFs, develop criteria and assess the
effectiveness of the implementation process of the project as researchers recommended above.
The author of this paper, as a team member of the ERP implementation project of EEU, has been
motivated to undertake this research. Therefore, this research tried to answer the following
questions.
1. To describe the extent to which the overall ERP implementation have been successful.
2. To determine the relationship between ERP implementation success and the five
management roles effectiveness.
3. To draw explanation based on the relationship between the management roles
effectiveness and ERP implementation success for the case of EEU.
Recently most of the organizations in Ethiopia have started to implement ERP technologies
toimprove their organization business management. Thus, to practitioners who are interested in
3
implementing ERP systems, it will provide valuable insights how best they can utilize their
limited resources.
It may also help as a reference material in future academic researches by filling the literature gap
on ERP implementation inEthiopian context.Thus, it will provide valuable insights for the
researchers to pay adequate attention to those factors that are most likely to have an impact upon
the implementation of the ERP system.
4
the study.All the reference materials used in this case study are listed under the reference part.
Additionally, the questionnaires and some statistical results are annexed with this paper.
Organizations that intend to implement ERP will meet three parties in the ERP market place
(Sneller, 2014). Firstly they have to select an ERP supplierthat a license agreement as well as
maintenance agreement is agreed with. Secondly, most organizations also use implementation
partners, consultancy firms that are specializedin ERP. Implementation partners offer a variety of
ERP-related service including advice on the use of best practices; model the ERP system, train
future users and support the migration, import or export of data from other information systems.
Finally, an ERP system can be kept up and running by application service provider, which
guarantees the availability and reliability of the ERP system for a predetermined group of users.
The application services can be outsourced or provided by the internal IT department.
The logical architecture of an ERP system, according to Sneller (2014), has three elements: ERP
interaction, ERP database, and ERP business logic. The ERP interaction element takes care of
the exchange of information between the ERP system and its environment. The ERP database
carries out the storage and retrieval of all data that are required for the correct functioning of the
ERP system. The ERP business logic consists of a large number of best practices that are either
programmed in the system or can be configured. The logical ERP system has to be installed on a
physical IT architecture: the main, the client-server, and the browser architectures.
Once an organization has implemented an ERP system it will use the system for several years. In
this long ERP life cycle a number of phases can be distinguished: the ex-ante evaluation, the
configuration and roll out, the go live, and the onward and upward phase (Sneller, 2014). The ex-
ante is the pre-selection of ERP suppliers, implementation partners and application service
5
providers. The configuration and roll out principle is the sourcing basis between the
implementation partner's consultants and the organization's employees that can vary from turn-
key to do-it-yourself. The go live principle is the model-building strategy that the choices are big
bang or some form of phasing. The onward and upward is the longest phase that the benefits of
the ERP implementation will only be realized.
Regarding operational benefits, cost, performance, quality and cycle time can all be benefitted
through ERP. The interaction between different business functions and information can be
improved (Alsalem, 2008). The quality of information increases and the time taken to complete
tasks are reduced by a large extent. According to Harris (2017), managerial benefits include
planning and decision making of managers and these can be improved by ERP
systems;businesses can grow and have innovations with the help of ERPto gain strategic
benefits; through IT infrastructure, the ERP system can provide flexibility to balance them if any
changes are to occur in the current scenario or in the future; andorganizational benefit of theERP
system is bringing a common vision and idea to empower the employeeseffectively. Johansson
6
(2012) identified intangible benefits due to ERP implementation such as increased flexibility,
better customer satisfaction, improved resource utility, and improvement in accuracy and better
decision making ability.
Despite theintended benefits, many researchers have concluded that many organizations have
been unable to make use of the ERP systems successfully (Harris 2017; Chao & Baptista,
2009).Most ERP systems tend to be large, complicated, and expensive (Al-Fawaz et al., 2008).
Moreover, ERP implementation requires an enormous time commitment from an organization’s
information technology department or outside professionals.
In addition, because ERP systems affected most major departments in a company, they tended to
create changes in many business processes. According to Al-Fawaz et al. (2008); Shang
&Seddon (2002), putting ERP in place requires new procedures, employee training, and both
managerial and technical support.
According to Kanhaiya (2006), to get the most from the software, organizations have to get
people inside company toadopt the work methods outlined in the software. If the people in the
different departmentsdon’t agree that the work methods embedded in the software are better than
the ones theycurrently use, they resist using the software or want IT to change the software to
match theways they currently do things. IT gets bogged down in long, expensive customization
effortsto modify the ERP software to fit with existing business practices. Customizations make
thesoftware more unstable and harder to maintain. Because ERP covers so much of what
abusiness does, failure in the software can prove costly. This is where ERP projects breakdown.
Kanhaiya (2006) argued that the migration from legacy system to ERP is a very serious business
and requires highlevel of involvement from top management. The shift should be taken as a
strategic decisionrather than cosmetic change. Risk, reward and costs involved are high and
7
expectations fromthe shift should be rationally optimal rather than what the consultants say.
Changemanagement and training aspects need special attention and should be taken up before,
duringand after the project implementation.
In order to obtain the benefits organizations have to plan ERP implementation carefully (Dezar
& Ainin, 2011). ManyERP projects have been delayed, reported as being over budget and have
required additional funding (Zhang et al., 2005). In addition, the ERP system is perhaps thesingle
largest IT investment an organization can make (Teltumbde, 2000). Therefore, according to
Dezar and Ainin, it is important to understand which factors contribute to the occurrence of
problemsand identify ways to overcome them.
A major problem with ERP case studies is that very few implementation challenges resulting in
these failures have been reported in the literature, and thus the reasons implementations failure is
not known to practitioners or researchers (Otieno, 2010). According to Otieno, this is a
motivation for researchers towards conducting empirical studies to explore challenges that affect
ERP systems implementation; because, identifying challenges relevant to local companies is one
way to increase the chances of a successful local ERP implementation.
Implementation success deals with the issues of how to succeed through an ERPimplementation
and it covers aspects such as ERP project success and failuredefinitions, problems and outcomes,
critical success factors and risk management(Esteves& Pastor,2001).Critical Success Factors
(CSFs) are elements related to the adoption and installation of ERP that arethought to lead to
successful implementation (Afanehet al., 2015).
The concept of CSFs was developed in the early 1960s. According to AlQashami & Mohammad
(2015), Ronald Daniel first discussed the idea of CSFs in the management literature, stating that
informationanalysis must focus on “success factors” when as a new approach to help achieve
organizationalgoals. The process of identifying CSFs helps to ensure that these factors receive
thenecessary attention and are carefully managed by an organization. CSFsare the few key areas
where things must go right for the business to flourish and for themanager’s goals to be attained.
CSFs, if addressed, significantly improve project implementation chances. Therefore, in the ERP
context, CSFs can be defined as a set of activities that need special considerationsand continual
attention for planning and implementing an ERP system. They can also be defined as factors
8
needed to ensure a successful ERP project. Thus, CSFsare particularly useful, as they provide
clear insight and guidance on where to focus specialconsideration and resources and continual
attention in planning for successful ERP project implementation.
An ERP process involves an overabundance of factors that impact the implementation to varying
degrees (Frimpon, 2012).Thus, many researchers tried to outline and discuss the key factors that
contribute to ERP success.Most of the studies carried on CSFs areas lack theoretical basis that
successfully link the critical success factors toimplementation outcomes of any kind (Otieno,
2010). Besides, there is no consensus on CSFs owing to difference in context between
implementing organizations (Leopoldo & Otieno, 2005).
According to Esteves & Pastor (2001), adequate ERP implementation methodologies were
pointed out as a criticalsuccess factor. However, there is a lack of studies about the definition,
usage andadequacy of these methodologies and their value in ERP projects.There is the need to
develop approachesto put in practice and manage the CSFs identified in some studies.The
development of techniques and approaches for the control and monitoring ofERP
implementation projects is an area to be improved. It is also important to relate CSFs with
implementation methodologies.
9
According to Kronbichler et al. (2010), a recommendation which model should beused or which
one is the best is not possible. Each model has its own area ofapplication and sometimes a
specific measurement approach based, for instance, on differentsystems or different stakeholders
involved. Their research paper shows some of the mostimportant models developed in the
literature and an overview of the different approaches of themodels to analyze the strengths,
weaknesses and the cases in which the specificmodel could be used is made.
A process that has many positive attributes but carries with it the risks of cost and schedule
overruns as wellas dreadfully low-success rate figures is necessarily a complex one.The main
reason for the complexity of an ERP implementation process is the vast array of variables
encounteredin the planning, execution and monitoring process. The complexity is further
magnified by the overwhelming number of interactions and relationships between the variables.
10
This complex exercise can only be managed using tried and tested project management
principles (Frimpon, 2012).
Thus, by using a compiled list of CSFs from other research work, Frimpon (2012) identified 28
unique CSFs by his paper. According to him, this number is very large for any software process
that with such alarge number there is the likelihood that many may have conflicting objectives.
Therefore, it is helpful to bringsome structure into the process by placing the possibly conflicting
CSFs into separate groups where they maytogether help achieve a sub-objective of the main ERP
objective of a successful implementation. Groupingcriteria can help the process of checking
whether the set of criteria selected is appropriate to the problem, canease the process of
calculating criteria weights in some methods, and can facilitate the emergence of higher
levelviews of the issues.
As shown in Figure 1, the criteria are the CSFs. A role is defined as a group ofCSFs identified
and put together for the purpose of achieving a sub-objective. Thus, roles are sets created to
holdspecific CSFs that help the attainment of the main objective. In this structuring exercise, the
CSFs are placed inroles according to the following criteria: 1) Function: Identify the CSFs
necessary to achieve the goals and objectives; and 2) Best measure: Many other CSFs can be
measures of the role but this CSF is the best or among the best.
11
2.5.1.The Top Management Role
The top management role includes goals and vision, version, strategy, support, delegate the
decisions, and champion (Frimpon, 2012).
Goals and vision: Goals should be clearly defined and well-understood (Shanks et al., 2000). A
good business vision is also helpful because it reduces the effortof capturing the functionality of
the ERP business model and therefore minimizes the customization effort (Esteves & Pastor,
2000).Visioning and planning requires articulating a business vision to the
organization,identifying clear goals and objectives, and providing a clear link between
businessgoals and IS strategy (Finney& Corbett, 2007).
Version: The choice of the correct ERP version has to be decided upon. An older version
mayresult in frequent updating (Esteves & Pastor, 2000). This is especially true in Africa where
thetendency is for officials to purchase the most outmoded software and other productsfrom
China and the West.
Strategy: This includes management decisions concerning how the software package is to
beimplemented. There are different approaches to ERPimplementation strategy ranging from
'phased' to 'big-bang' implementations (Panorama Consulting Solutions 2019), centralized versus
decentralized (Siriginidi, 2000). Also there is the benefit of introducing a new system
andcompletely forgetting about the legacy system (Finney & Corbett, 2007).
Support: Management support is important for accomplishing project goals and objectives
andaligning these with strategic business goalsin terms of theirown involvement and the
willingness to allocate valuable organizational resources.It has been empirically proven that
strong and committed leadership at the topmanagement level is essential to the success of an
ERP implementation (Finney& Corbett, 2007).
Decisions delegation: Project team members must be empowered to make quick decisions to
reduce delays inimplementation related with slow decision-making. Organizationsshould attempt
to make decisions as rapidly as possible, as even small delays can havean impact on such a long-
term project.
12
Champion: The role of the project champion is very important for marketing the
projectthroughout the organization. The champion is really an ERP projectadvocate.The
individual should possess strong leadership skills, as well as business, technicaland personal
managerial competencies (Finney& Corbett, 2007).
H1. Effective top management role has a strong and positive relationship with ERP implementation
success.
Hardware and software: Management must make a careful choice of an ERP package that best
matches thelegacy systems, e.g. the hardware platform, databases and operating systems.
Thesuitability of software and hardware refers to the fit between the selected ERP systemand the
hardware. Lack of data software quality and reliability and the hardware,software difficulties
lead to ERP failure (Singhal et al., 2011).
Data accuracy: Data loaded from existing legacy systems must be of high quality. Datamust be
cleansed and transferred to the ERP system to ensure no disruption toperformance, high quality
data is very important in the integrated environment of an ERP system (Shanks et al., 2000).
Configuration: Configuring the software and making it actually useful to the business is an
aspect ofERP implementation that no business manager is ever willing to face.Serious attention
should be given to the conference room pilot (CRP), which provides ademonstration of the ERP
system that users can test drive before the systemconfiguration is locked down. The system
should not be under configured. It canbecome a nightmare to spend many months designing and
building a system, just to have it perform slowly out of the gate (Swartz & Orgill, 2001).
Monitor system performance: Milestones and targets need to be actively monitored to track the
progress of an ERPproject indicated that projectmanagement-based criteria should be used to
measure against completion dates, costs,and quality and operational criteria should be used to
measure against the production system (Nahet al., 2003). The monitoring of performance arevery
critical factors in ensuring the success of any organization (Yingjie, 2005).
13
Testing and troubleshooting: Troubleshooting errors is critical. Rigorous and
sophisticatedsoftware testing eases implementation. Development and testingperspectives unique
to ERP projects must be well-thought-out and managed (Nah et al., 2003).
H2. Effective technology management role has a strong and positive relationship with ERP
implementation success.
Consultant support: Considering the staff, an advantage could be obtained by the quick
andsubstantial transfer of knowledge from consultants to qualified staff, creatingthe possibility
for them to participate to the tasks of external consultants or even to takethem over. In fact, it is
imperative to arrange for knowledge transfer from theconsultant to the company so as to
decrease the dependency on the vendor/consultant (Finney & Corbett, 2007).
Vendor support: Companies purchase ERP packages from foreign ERP vendors and ERP
represent the best-practice processesthat is different from organizational business process, thus,
it’s important to getthe vendor's support. Software vendors should be carefully selected since
they play acrucial part in shaping the ultimate outcome of the implementation (Panorama
Consulting Solutions, 2019).
Standardization: Organizations should be willing to change their businesses to fit the software in
order to minimize the degree of customizations needed (Shanks et al., 2000). Wherever and as
far as possible, the ERP-hosting organization should try to adopt theprocesses and options built
into the ERP, rather than seek to modify the ERP to fit theparticular business practices.
Organizations should be committed to the idea of implementing the unadulterated orbasic
version with no or minimal customization (Finney& Corbett, 2007). That is the ultimate
instandardization.
Customization: Even the most robust out-of-the-box ERP functionality might need to be
customized tofit the business. The possibilities of such customizations should be addressed
upfrontversus during mid-deployment, in order to have better control over the costs.The
14
management of the tradeoffs between customization and standardization is a key toa successful
implementation (Finney& Corbett, 2007).
H3. Effective process management role has a strong and positive relationship with ERP
implementation success.
User involvement: A major cause of ERP failure is lack of employee involvement (Barker &
Frolick, 2003). User involvement and participation will result in a better fit of user
requirementsachieving better system quality, use and acceptance. Statistical results show that
lack ofend user involvement can cause the ERP process to have difficulties (Lee & Lee, 2001).
Education and training: The most measured subset of costs is the initial software development
efforts while themost uncertain and often the largest cost is long-term maintenance and training
(Hubbard, 2007). Users can only gain an appreciation of the utility of the system only if they are
well trained to use it. Insufficient training causes significant negativeimpact on ERP systems
implementation (Lee& Lee, 2001).
Discipline: Ensuring that a complex change like that associated with a transcendental
informationsystem that gets the right results, in the right timeframe, at the right costs, requires
aparadigm change in an attitude as basic as discipline. This can be improved
throughindoctrination at meetings to address attitudinal changes.Lack of discipline, resistance,
15
and lack of broad-based companycommitment are the major factors that slow down the process
of implementation (Zhanget al., 2003).
Commitment: Sustained management commitment, both at top and middle levels during
theimplementation, in terms of their own involvement and the willingness to levels duringthe
implementation, in terms of their own involvement and the willingness to allocatevaluable
organizational resources. The need for organizationalcommitment should be stressed during
strategy sessions because a lax in that can scupper the project (Zhang et al., 2003).
H4. Effective change management role has a strong and positive relationship with ERP
implementation success.
Needs assessment: One of the first steps involves evaluating the needs and requirements that will
drive theimplementation of an ERP system. A needs assessment with a definition ofrequirements
is essential not only to guide the start of the project, but also to gauge thesuccess of the project
after completion. The basic description of needs should be refinedto a set of specific institutional
acceptance criteria at an early phase of the project. Thisstatement will be used at a later date to
help evaluate the success of the project in meeting these goals (Swartz & Orgill, 2001).
Competent team: A dedicated and competent staff is a must. Esteves & Pastor (2000)lists this
factor as one of the critical success facts. Furthermore, researches examined the relationship
between CSFs and ERP system performance, among the CSFs identifiedwas maintaining
excellent staffing (Wen et al., 2003).
Heterogeneous team: ERP projects typically require some combination of business, information
technology, vendor, and consulting support. The structure of the project team has a strong impact
inthe implementation process. Two important factors are the integration of third-partyconsultants
within the team and the retention within the organization of the relevant ERP knowledge
(Esteves & Pastor, 2000).
16
Formalize plan: A single integrated project plan, not a collection of independent plans, can’t
berolled into a summary report to management (Swartz & Orgill, 2001). This means to have a
well-defined plan/schedule for all the activities involved in the ERP implementation,with an
appropriate allocation of budget and resources for these activities. Evidenceshows that the
majority of projects fail to finish the activities on time and within budget (Esteves & Pastor,
2000).
Partnership: During the implementation phase there are different partners involved such
asconsultants and software and hardware vendors. An adequate partnership between themwill
ease achievement of the goals defined (Esteves & Pastor, 2000). The project leadership must
engender trust and avoid attrition and unnecessary competition among members.
Scope management: This factor is related with concerns of project goals clarification and their
congruencewith the organizational mission and strategic goals. This includes both
scopedefinition and subsequent scope control. Some components of this factor are: scope
ofbusiness processes and business units involved, ERP functionality implemented, technology to
be replaced/upgraded/integrated, and exchange of data (Esteves & Pastor, 2000). Avoid Scope
creep, which is clearly delineating and effectively limiting the scope ofthe project. While new
functionality shouldn’t be rejected outright, hard decisionshave to be made to keep the project
from careening out of proportion (Swartz & Orgill, 2001). When there are unrealistic
17
expectations from the ERP, poor estimation of its scope and size,it creates a mess and the
realistic goals are lost.
H5. Effective project management role has a strong and positive relationship with ERP
implementation success.
18
2.6. Dependent and Independent Variables of the Study
This case study tried toassess the ERP implementation success of EEU against the five
management roles by adapting the Frimpon's re-structured CSFs “role” model for ERP
implementations (fig.2). As described above, the model grouped the CSFs into roles that can
ease the calculation their weight in relation to the specific objectives and can ease the weight
calculation of the roles in relation with the general objectives of this study. The author of this
paper has also considered the model's roles and CSFs familiarity with the sample population in
the study and would greatly enable assessment of the ERP implementation success in EEU.
The roles are the pillars that shoulder the burden of the implementation of the ERP process.A
weakness in any of the pillars can result in a failure. On the other hand, allthe pillars have to be
managed well to result in a successful implementation (Frimpon, 2012).
19
Chapter Three: Research Methodology
3.1. Research Strategy
As presented in the previous chapter, a review of the literatures on CSFs for ERP system
implementation process regarding the management roles were conducted in order todevelop
research framework that associate the roles effectiveness with the ERP implementation success
for the case of EEU.According to Yin (2003), case studies can be used to explain, describe or
explore events, or phenomena in the everyday contexts in which they occur and in turn can help
to understand and explain casual links and pathways resulting from a new policy initiative or
service development. Thus, various data collection methods can be employed and used in
combination. Therefore, this research followed a mixed approach methods (i.e. combination of
quantitative and qualitative).
This case study is conducted in EEU to assess the opinions of different participants in the project
of ERP system implementation, to describe the extent to which the overall ERP implementation
success have been met related to management roles effectiveness and test the formulated
hypotheses to draw explanation. Therefore to achieve the objectives the study, descriptive
research design methodused to describe and draw explanation.
Since the scope of this research focuses in the first go live and roll out phase of the project, the
target population is consist of members of the ERP program management office and end users
20
found in Addis Ababa. Thus, the total number of end users has to be counted from head quarter,
7 different locations and 75 customer service centers. So that, end users from 219 regional
business locations outside Addis Ababa are not targeted.
To determine sample sizeusing Yamane sample calculating technique, n = N/(1+Ne2), with 95%
confidence level and 5% margin of error, a sample size for a population size for 364will be
approximately 190.However, due to inaccessibility of some interviewees and survey respondents
due to location, busy office works and the overall time constraint of the research program, for
this study a total of 167purposively selected samples are used.In order to discuss the relationship
between the dependent and independent variables, 3 samples (all the 1 project manager and
2purposively selected consultants/implementing partners) areselected.Additionally, to describe
the ERP implementation success,questionnaire is distributed to a sample of 3 package leads,
5core process leads and 156end users.
Package leads and core process leads, as they are deployment team members during the
implementation, are selected purposely and are asked qualitative questions to share their
experience of what worked well, what could have been done better and recommendation for
future endeavors. The end users, as they are currently operating on the system on a daily basis
around the dispersed geographical business locations found in Addis Ababa, are respond
quantitative Likert scale questionnaires using nonrandom techniques. Thus, in order to address
all business areas found in Addis Ababa almost equal quota isgiven module package level, that
21
is, 77ERP Enterprise Core Component (ECC) and 79Customer Centric Application (CCA) end
users are selected.
According to Saunders et al. (2008), the confidentiality of the data that wouldhave to be provided
and the anonymity of the organization or individual participants have to be assured. Therefore,
clear assurances about these aspects need to be provided and promised. Thus, an introductory
letterisgiven to guarantee at the time of making the request for access by writing not to share
rawdata with anyone and assurances aboutanonymity and confidentiality to participants.
22
Chapter Four: Data Presentation, Analysis and Interpretation
4.1. Demographic Information of End Users Respondents
The total number of end users respondents is 156. Their demographic data isshown in the
following tables below.Data is gathered proportionally from all functional areas located in Addis
Ababa. From the category of 156 respondents of end users, as presented in Table 2 below, 49.4%
are Enterprise Core Component (ECC) and 50.6% are Customer Centric Applications (CCA)
package users.
Table 2. Demographic data of the end user respondents. Source primary data 2019
Age
Gender
Year of experience
30-40 1 .6 .6 100.0
23
Highest level of education
ERP Module
The results in this category indicate the organization has to work more on Decision Delegation,
Championing, Supporting and outlining Strategy.
24
Table 3. Total effectiveness of the Top Management Role. Source primary data 2019
Table 4. Total effectiveness of the Technology Management Role. Source primary data 2019
As the overall result indicates, EEU needs improvement in giving serious attention for system
configuration (3.2179) and managing tests unique to the ERP system (3.2308), mainly the
organization has to work more on cleansing and loading the existing legacy data for data
accuracy and quality.
25
effective among the rest CSFs grouped in the category. The rest CSFs in this category get mean
values of Customization (2.7564), Vendors Support (2.8269), and Standardization (2.9744).
Table 5. Total effectiveness of the Process Management Role. Source primary data 2019
Therefore, the Consultant Support needs the most improvement in considering quick and
substantial transfer of knowledge related to others CSFs of this category.
Table 6. Total effectiveness of the Change Management Role. Source primary data 2019
The result shows that User Involvement, Organizational Culture, Education and Training,
Discipline, and Commitment are not effective. In this category, as shown in Table 6, Education
and Training is the least effective among the grouped CSFs which scored the largest mean value
(4.1410), and the rest get mean values of change in Organizational Culture (3.7628), Discipline
improvement (3.6154), Users Involvement (3.3333), and Commitment sustainment (3.2949).This
indicates, the overall change management practices are the most crucial role area that EEU needs
the most attention and improvement related to the others roles.
26
4.2.5.The Project Management Role
This role has the greatest numbers of CSFs compare to the others management roles, that is, it is
a group of eight CSFs. Their measurement is presented in the Table 7 below.
Table 7. Total effectiveness of the Project Management Role. Source primary data 2019
The result shows that Needs Assessment (2.8718), Competent Staff (2.7436), Coordination
(2.5769), Formalized Plan (2.5256), Team Composition (2.4744) are scored the highest
effectiveness. Team Composition is the best scored CSF among the group as it scored the least
mean score. The result also shows Partnership (3.0641) and Scope Management (3.1154) are less
effective, and Leadership (3.3013) needs the most attention.
27
This result indicates that the ERP implementation is not adequately successful. Because, the
mean indicates the overall ERP Implementation Success is above the adequate scale of 3.
Reliability Statistics
.783 6
The Corrected Item-Total Correlation result, Table 10, also shows all values of the scales
reliability is .748 maximum and .564 minimum.
Item-Total Statistics
28
This indicates the degree to which each items correlates with the total score. According to Pallant
(2005), low values (less than .3) indicate that the item is measuring something different from the
scale as a whole. Therefore the study's scale fulfills the reliability requirement.
• if the correlation value is between .10 and .29, it indicates small relationship,
• if the correlation value is between .30 and .49, it indicates medium relationship, and
• if the correlation value is between .50 and 1.0, it indicates large relationship.
The results indicate that the highest correlation between the Total ERP Implementation Success
and the independent variables effectiveness; i.e., .541 with Top Management, .597 with
Technology Management, .492 with Process Management, .549 with Change Management, and
.627 with Project ManagementRole (see Table 11). All the results are between 0 and +1 and it
29
can be concluded that, there is a strong and positive relationship between the ERP
Implementation Success and the effectiveness of the five Management Roles.
Correlations
Pearson ** ** ** ** **
ERP 1 .541 .597 .492 .549 .627
Correlation
Implementation
Sig. (2-tailed) .000 .000 .000 .000 .000
Success
N 156 156 156 156 156 156
Pearson ** ** ** ** **
.541 1 .687 .389 .357 .534
Total Top Correlation
Management Role Sig. (2-tailed) .000 .000 .000 .000 .000
N 156 156 156 156 156 156
Pearson ** ** ** ** **
.597 .687 1 .448 .335 .495
Total Technology Correlation
Management Role Sig. (2-tailed) .000 .000 .000 .000 .000
N 156 156 156 156 156 156
Pearson ** ** ** ** **
.492 .389 .448 1 .498 .401
Total Process Correlation
Management Role Sig. (2-tailed) .000 .000 .000 .000 .000
N 156 156 156 156 156 156
Pearson ** ** ** ** **
.549 .357 .335 .498 1 .493
Total Change Correlation
Management Role Sig. (2-tailed) .000 .000 .000 .000 .000
N 156 156 156 156 156 156
Pearson ** ** ** ** **
.627 .534 .495 .401 .493 1
Total Project Correlation
30
This case study tries to examine the relationship between the ERP Implementation and the five
Management Roles by formulating the following hypotheses;
H1. Effective top management role has a strong and positive relationship with ERP implementation
success.
H2. Effective technology management role has a strong and positive relationship with ERP
implementation success.
H3. Effective process management role has a strong and positive relationship with ERP
implementation success.
H4. Effective change management role has a strong and positive relationship with ERP
implementation success.
H5. Effective project management role has a strong and positive relationship with ERP
implementation success.
As shown in the correlation statistics result, 156 cases are included and there is no missing
information on all variables, the direction and strength of the relationship between the dependent
variables and all independent variables is positive and strong, and correlation is significant at the
0.01 level (2-tailed).
To get an idea of how much variance the variables share bycalculating the coefficient of
determination,we can square ther value (multiply it by itself) and convertthis to ‘percentage of
variance’ just multiply by 100 (Pallant, 2005). Therefore;
• Top Management Role has .541, thus, its coefficient of determination is 29.27%,
• Technology Management Role has .597, thus, its coefficient of determination is 35.64%,
• Process Management Role has .492, thus, its coefficient of determination is 24.21%,
• Change Management Role has .549,thus, its coefficient of determination is 30.14%, and
• Project Management Role has .627, thus, its coefficient of determination is 39.31%.
These results indicate all the independent variables have a respectable amount of variance to
explain the ERP Implementation Success. Therefore, all the hypotheses of this case study are
accepted.
31
4.6. Qualitative Analysis
This section presents the qualitative analysis of the open ended questions and the interview for
the research's variables. The open ended questionnaires were distributed for eight core team
members, and semi structured interviews were held with one application project manager and
two implementation partners.
32
4.6.4.Change Management Role
All the respondents are disagreed with the effectiveness of this management role. They
recommended that users involvement have to be improved to achieve better system quality, use
and acceptance; the mentality change from using reams of paper to electronic media have to
beencouraged; education and training have to be sufficiently given to users;and the company
should work hard in attitudinal changes and organizational commitment have to be sustain both
at top and middle level management.
4.6.7.Interview Responses
The result of the semi structured interviews also shows that the effectiveness of the five
management roles is highly related to the success of ERP implementation and the five
management roles can equally influence the success. According to their response, the day to day
challenges faced when implementing ERP system need to be monitored, captured, analyzed and
proper corrective actions should have to be taken. Otherwise, the result would severely harm the
organization. They have also mentioned that the company needs more things to do regarding the
five management roles, Top Management, Technology Management, Process Management,
Change Management and Project Management roles areas.
33
4.7. Discussion on the Findings
ERP is an enterprise-wide information system designed to coordinate all the resources,
information, and activities needed to complete business processes. It supports the business
system that maintains a single database for a variety of business functions such as
Manufacturing, Supply Chain Management, Financials, Projects, Human Resources, Enterprise
Asset Management, Quality Management, Customer Relationship Management,and Decision
Support Systems. Thus ERP system implementations are huge investments and consume an
organization's financial resources and are in turn expected to bring about benefits in operational
effectiveness, accountability, transparency, decision making and client satisfaction.
Many research works reviled that there is no easy way to implement an ERP system because the
implementation process is a disruptiveundertaking for any organization. It requires steady
leadership, significant resource investment, theright system integrator as well as a detail project
plan and communication strategy. Ultimately, ERPsuccess requires a thorough analysis and
integration of people, processes and technology.
EEU has more to doin order to the top management role be effective. The top management
requires articulating a business vision to the organization, identifying clear goals and
objectives(Shanks et al., 2000), and providing a clear link between business goals and IS strategy
(Finney & Corbett, 2007).The choice of the correct ERP version has to be decided upon. An
older version may result in frequent updating (Esteves & Pastor, 2000). Clear strategies must be
outlined to benefit from introducing a new system andcompletely forgetting about the legacy
system (Finney & Corbett, 2007).Strong and committed leadership at the topmanagement level is
essential to the success of an ERP implementation (Finney & Corbett, 2007).Project team
members must be empowered to make quick decisions to reduce delays inimplementation related
with slow decision-making.The individual should possess strong leadership skills, as well as
34
business, technicaland personal managerial competencies to advocate the ERP project (Finney &
Corbett, 2007).
Management must make a careful choice of an ERP package that best matches thelegacy
systems, e.g. the hardware platform, databases and operating systems (Singhalet al.,
2011).Datamust be cleansed and transferred to the ERP system to ensure no disruption
toperformance, high quality data is very important in the integrated environment of an ERP
system (Shanks et al., 2000).Serious attention should be given to the conference room pilot,
which provides a demonstration of the ERP system that users can test drive before the
systemconfiguration is locked down (Swartz & Orgill, 2001).Project management-based criteria
should be used to measure against completion dates, costs,and quality and operational criteria
should be used to measure against the production system (Nah et al., 2003). The monitoring of
performance arevery critical factors in ensuring the success of any organization (Yingjie, 2005).
Development and testingperspectives unique to ERP projects must be well-thought-out and
managed (Nah et al., 2003). When these criteria are fulfilled, the technology management roles
become effective.
In order to the process management role be effective; it is important to arrange for knowledge
transfer from theconsultant to the company so as to decrease the dependency on the
vendor/consultant (Finney & Corbett, 2007).Software vendors should be carefully selected since
they play acrucial part in shaping the ultimate outcome of the implementation(Panorama
Consulting Solutions, 2019).Organizations should be willing to change their businesses to fit the
software in order to minimize the degree of customizations needed (Shanks et al., 2000).
Organizations should be committed to the idea of implementing the unadulterated orbasic
version with no or minimal customization (Finney& Corbett, 2007). The management of the
tradeoffs between customization and standardization is a key toa successful implementation
(Finney& Corbett, 2007).
This study indicates the change management role needs great attention. A major cause of ERP
failure is lack of employee involvement (Barker & Frolick, 2003). Statistical results show that
lack ofend user involvement can cause the ERP process to have difficulties (Lee & Lee, 2001).
Aculture with shared values and a strong corporate identity that is conducive to change iscritical.
In the local context, the mentality change from using reams of paper to electronic media should
35
be encouraged, and ERP facilitates that (Nah et al., 2003).The most measured subset of costs is
the initial software development efforts while the most uncertain and often the largest cost is
long-term maintenance and training(Hubbard, 2007). Users can only gain an appreciation of the
utility of the system only if they are well trained to use it. Insufficient training causes significant
negativeimpact on ERP systems implementation (Lee & Lee, 2001).Lack of discipline,
resistance, and lack of broad-based companycommitment are the major factors that slow down
the process of implementation (Zhang et al., 2003).The need for organizationalcommitment
should be stressed during strategy sessions because a lax in that can scupper the project (Zhang
et al., 2003).
The project management role is also the other area that needs more improvement as the result of
this study. One of the first steps involves evaluating the needs and requirements that will drive
theimplementation of an ERP system. The basic description of needs should be refinedto a set of
specific institutional acceptance criteria at an early phase of the project. Thisstatement will be
used at a later date to help evaluate the success of the project in meeting these goals (Swartz &
Orgill, 2001).A dedicated and competent staff is a must (Esteves & Pastor, 2000; Wen et al.,
2003).ERP projects typically require some combination of business, information technology,
vendor, and consulting support, which is the integration of third-partyconsultants within the team
and the retention within the organization of the relevant ERP knowledge (Esteves & Pastor,
2000). A single integrated project plan, not a collection of independent plans, can’t berolled into
a summary report to management (Swartz & Orgill, 2001). Evidenceshows that the majority of
projects fail to finish the activities on time and within budget (Esteves & Pastor, 2000).Good
coordination and communication between implementation partners are essential (Nah et al.,
2003). The communication effort should be done in a regular basis during the implementation
phase (Esteves & Pastor, 2000). In order to successfully accomplish the decision to implement
anERP system, the effective project management comes into play to plan, coordinate and control
such an intricate project (Yingjie, 2005).The project leadership must engender trust and avoid
attrition and unnecessary competition among members(Esteves & Pastor, 2000). Scope
management is related with concerns of project goals clarification and their congruencewith the
organizational mission and strategic goals. Avoid Scope creep, which is clearly delineating and
effectively limiting the scope of the project (Swartz & Orgill, 2001).The Project leader needs
leadership skills and respect of project members and administration (Swartz & Orgill, 2001).
36
Chapter Five: Conclusion and Recommendation
5.1. Conclusion
This case study tried to assess ERP implementation successbased on five management roles and
draw explanations based on those management roles;by using a review of related literatures on
CSFs criteria for ERP system implementation in order to develop research framework that
associate the management roles effectiveness with the ERP implementation success; and also by
using various data collection methods (qualitative and quantitative) in combination with
nonrandom sampling techniques to select 167 samples and using the opinions of the project
managers, core team members, end users and consultants/implementation partners assessed the
implementation success, test the relationship and draw explanation.
1. It describes the overall ERP implementation success based on those management roles is
below average.
2. It examined the relationship of ERP implementation success with CSFs criteria (the five
management roles) by exploring the correlation statistics using SPSS 20 software, thus, the
result showed there is a strong and positive relationship between ERP implementation
success and the effectiveness of each management roles.
3. All the five management roles have a respectable amount of variance to explain the ERP
Implementation Success.
5.2. Recommendation
EEU can consider the five management roles effectiveness identified in this study as inputto
improve the second phase of the project. Specially;
• The Top Management should work hard in; outlining the best strategies by analyzing and
choosing from the possible alternatives; supporting the project with strong and committed
leadership; empowering the project team for timely decision making; and championing
the project by developing the required transformational leadership skills.
37
• The company should give more attention for the of accuracy legacy data to test the
system with proper knowledge to manage troubleshooting before configuration locked
down.
• The company should consider the essence of knowledge transfer gained from the external
consultants to decrease the dependency on them.
• Changes have to be well managed by involving and participating users of the system for
shared values, attitudinal changes, sustained commitment, and sufficient training and
education.
• The company should develop the competency of project management in building strong
partnership with consultants and vendors, scope definition and control, and the ability to
effectively and efficiently run such complex projects.
Each management roles can be a research topic for further research. Other Ethiopian
organizations planning to implement ERPsystem can consider implementing all management
roles identified in this study asinput for managing their ERP project.
38
References
Afaneh, S., AlHadid, I.,& AlMalahmeh, H.2015.Relationshipbetween organizational factors,
technological factors and enterprise resource planning system implementation.International
Journal of Managing Information Technology, 7(1), 1-16. Retrieved April 20, 2019, from
http://www.ijmit.com.pdf
Akiki, P. A., Arosha K. Bandara, A. K., Maalouf, H. W., & Yu, Y. 2012.A systematic
framework for assessing the implementation phase of ERP systems [Technical Report 2012/ 06].
The Open University, Walton Hall, Milton Keynes, MK7 6AA, United Kingdom. Retrieved May
25, 2019, from http://computing.open.ac.uk.pdf
Al-Fawaz, K., Al-Salti, Z., & Elbadi, T. (2008, May 25-26). Critical success factors in ERP
implementation: A Review[conference paper]. European and Mediterranean Conference on
Information Systems, Dubai. Retrieved May 25, 2019, from http://www.emcis.com.pdf
Al Qashami, A.,& Mohammad, H. 2015. Critical success factors for implementing an ERP
system within university context: Concepts and literature review.International Journal of
Managing Information Technology, 7(4), 1-19. Retrieved June 24, 2019, from
http://www.ijmit.com.pdf
Al-Rawashdeh, T. A., Al’azzeh, F. M., & Al-Qatawneh, S. M. 2014. Evaluation of ERP systems
quality model using analytic hierarchy process (AHP) technique.Journal of Software
Engineering and Applications, 7, 225-232. Retrieved April 20, 2019, from
http://www.scirp.org/journal/jsea.pdf
Alsalem, A. 2008. Benefits and limitations of implementing ERP systems in Saudi organizations,
SSRN Electronic Journal. Retrieved March 19, 2019, from http://www.ssrn.com.pdf
Azad, N., Shadmanfard, A., &Zarifi, S. F. 2013. An exploration study to find important factors
influencing on enterprise resource planning.Management Science Letters, 3, 2405–2410.
Barker, T., & Frolick, M. N. 2003. ERP implementation failure: A case study.
InformationSystemsManagement,20(4), 43-49.
39
Batada, & Rahman. 2012. Measuring system performance &user satisfaction after
implementation of ERP [Proceedings]. Informing Science & IT Education Conference (InSITE).
Retrieved April 25, 2019, from http://dx.doi.org/10.1201/1078/43647.20.4.20030901/77292.7
Bokovec, K., Damij, T., & Rajkovič, T. 2015.Evaluating ERP projects with multi-attribute
decision support systems. Journal of Computers in Industry, 73, 93-104. Retrieved July 6, 2019,
from https://www.dl.acm.org database.
Chao P. G., & Baptista, N. M. 2009. Surfacing ERP exploitation risks through a risk ontology.
Industrial Management & Data Systems, 109(7), 926-942.
Dezdar, S., &Ainin, S. 2011. Examining ERP implementation success from a project
environment perspective.Business Process Management Journal, 17(6), 919-939. Retrieved
April 25, 2019, from www.emeraldinsight.com/1463-7154.htm.pdf
Esteves-Sousa, J., Pastor-Collado, J., & Casanovas, J. 2002.A framework proposal for
monitoring and evaluating training in ERP implementation projects[Technical Research Report].
Esteves-Sousa, J., & Pastor-Collado, J. 2000.Towards the unification of critical success factors
for ERP implementations [conference paper]. 10th Annual Business Information Technology
(BIT), Conference, Manchester.
Esteves-Sousa, J., & Pastor-Collado, J. 2001. Enterprise resource planning system research: An
annotated bibliography.Communications of AIS, 7(8), 1-52. Retrieved from AIS database.
Ethiopian Electric Power. 2015.Contract document for the supply and installation of enterprise
resource planning (ERP), customer centric applications (CCA) and decision support system
(DSS). Contract No.: EEP/ERP_CCA_DSS/ 01/2015.
Finney, S., & Corbett, M. 2007. ERP implementation: A compilation and analysis of critical
success factors.Business Process Management Journal, 13(3), 329-347.
40
Harris S. 2017. Evaluating the implementation of ERP system and its impact on the business
process: A case study on Sibca Electronics LLC[MA Dissertation]. Dept. of Business
Administration, Cardiff Metropolitan University.
Hubbard, D. 2007. How to measure anything. Retrieved from April 25, 2019, from
http://www.tacadvisory.com.pdf
Johansson, B. (2012). Exploring how open source ERP systems development impact ERP
systems diffusion. International Journal of Business and Systems Research, 6(4), 361.
Lee, C., & Lee, H. 2001. Factors affecting ERP implementation systems in a higher education
institution.Retrieved April 25, 2019, from http://iacis.org/iis/2001/LEE207.pdf
Leopoldo, E., & Otieno, J. 2005. Critical success factors of ERP implementation.Encyclopedia of
Information Science and Technology, 628-633.
Luo, W., & Strong, D. M. 2004.A framework for evaluating ERP implementation
choices.Transactions on Engineering Management, 51(3), 322-333. Retrieved from IEEE
database.
Nah, F. F., Zuckweiler, K. M., & Lau, J. L. 2003. ERP implementation: Chief information
officers perceptions of critical success factors. International Journal of Human–Computer
Interaction, 16(1), 5-22. Retrieved from IJHC database.
41
Pallant, J. 2005.SPSS Survival Manual: A step by step guide to data analysis using SPSS for
windows (2nded.). Retrieved from the SPSS Survival Manual website
http://www.allenandunwin.com/spss.htm.pdf.
Panorama Consulting Solutions. 2019. ERP Report: People/ Process/ Technology [report].
Retrieved June 9, 2019, from https://www.panarama_consulting.com.pdf
Saunders, M., Lewis, P., & Thornhill, A. 2009. Research methods for business students (5thed.).
Retrieved from Pearson Education website: http://www.pearsoned.co.uk.pdf
Shang, S., &Seddon, P. 2002.Assessing and managing the benefits of enterprise systems: The
business manager’s perspective.Information Systems Journal, 20(12), 271-299. Retrieved from
ISJ database.
Shanks, G., Parr, G. A., Hu, B., Corbitt, B., Thanasankit, T., & Seddon, P. 2000. Differences in
critical successfactors in ERP systems implementation in Australia and China: A cultural
analysis. Retrieved from http://aisel.aisnet.org/ecis2000/53/.
Shatat, A. S. 2017. Critical success factors in enterprise resource planning (ERP) system
implementation: An exploratory study in Oman.The Electronic Journal of Information Systems
Evaluation, 18 (1),36-45.Retrieved April 25, 2019, fromhttp://www.ejise.com .pdf
Singh, J.,& Singh, R. 2013. Enterprise resource planning systems in tourism industry.
International Research Journal of Management Sociology & Humanities, 4(3), 1352-1365.
Retrieved June 24, 2019, fromhttp:www.irjmsh.com.pdf
Singhal, S., Tandon, P., & Sharma, S., K. 2011. Critical success factors in implementation of
ERP in education. International Journal of Contemporary Practices, 1(1).
Siriginidi, S. R. 2000. Enterprise resource planning: Business needs and technologies. Industrial
Management& Data Systems, 100(2), 81-88. Retrieved April 25, 2019, from
http://www.idms.com.pdf
Sneller, L. 2014.A Guide to ERP: Benefits, Implementation and Trends(1sted.). Retrieved March
24, 2019, from http://www.bookboon.com.pdf
42
Swartz, D., &Orgill, K.2001. Higher education ERP: Lessons learned.Educause Quarterly,
24(2), 20-27.
Yin, R.K. 2003. Case study research: Design and method (3rded.). London: Sage.
Yingjie, J. 2005. Critical success factors in ERP implementation in Finland. Education and
Training, 2008(2001), 1-9.
Zhang, L., Lee, M. K., Zhang, Z., & Banerjee, P. 2003.Critical success factors of enterprise
resource planning systems implementation success in China[Proceedings].The 36th Hawaii
International Conference on System Sciences. Retrieved April 25, 2019, from
http://www.IEEE.com.pdf
Zouine, A., &Fenies, P. 2015. A new evaluation model of ERP system success.Journal of
Intelligence Studies in Business, 5(1), 18-39. Retrieved July 6, 2019, from https://ojs.hh.se.pdf
43
Annex 1 – Questionnaire for End Users
Addis Ababa University
School of Commerce
Dear Respondents
The questionnaire is based on your experience and involvement in EEU's ERP implementation.
The questionnaire is designed to evaluate the success of the ERP implementation by selected five
management roles. The findings of the study will propose possible solutions to the challenges
and setbacks encountered during the implementations and denote lessons learned for future
endeavors.
Effective Top Management Role: The top management role includes clearly articulating goals
and vision, approving the correct ERP version, outlining implementation strategy, support in
cash and kind, delegate the decisions, and champion/advocate the project.
44
Effective Project ManagementRole: The project management role includes needs assessment,
competent team, heterogeneous team, formalizes plan, coordination, partnership, scope
management, and leadership.
Year of Experience 1.0-10 years 2.10-20 years 3.20-30 years 4. 30-40 years
Strongly Strongly
No. The Top Management Role Agree Agree Neutral Disagree Disagre
Goals and Vision have been clearly articulated by the top
mangement, in order to reduce the effort of capturing the
1
functionality of the ERP business model and therefore
minimize the customization effort.
The top management has chosen the correct ERP version
2
in order to minimize frequent updating.
The top management has outlined implementation
3 strategy to benefit from introducing a new system and
completely forgetting about the legacy system.
The top management effectivelly support for
accomplishing project goals and objectives and aligning
4 these with strategic business goals in terms of their own
involvement and the willingness to allocate valuable
organizational resources.
The top management has empowered the project team
5 members to make quick decisions to reduce delays in
implementation related with slow decision-making.
The top management possess strong leadership skills, as
6 well as business, technical and personal managerial
competencies to advocate the ERP project.
45
Strongly Strongly
No. The Technology Management Role Agree Agree Neutral Disagree Disagre
The selected ERP system and the hardware best matches the
1
legacy systems.
Data loaded from existing legacy systems is cleansed, that is, it is
2
accurate and of high quality
Serious attention have been given to the conference room pilot,
3 which provides a demonstration of the ERP system that users can
test drive before the system configuration is locked down.
The progress of the ERP project have been monitored and
tracked to measure against completion dates, costs, and quality
4
and operational criteria should be used to measure against the
production system.
Development and testing perspectives unique to ERP projects
5
have been well-thought-out and managed.
Strongly Strongly
No. The Process Management Role Agree Agree Neutral Disagree Disagre
Consultat support have been effective, considering
quick and substantial transfer of knowledge from
1 consultants to qualified staff in creating the
possibility for them to participate to the tasks of
external consultants or even to take them over.
Software vendors have been carefully selected since
2 they play a crucial part in shaping the ultimate
outcome of the implementation.
The organization have been committed to the idea
3 of implementing the unadulterated or basic version
with no or minimal customization.
The management of the tradeoffs between
customization and standardization have been
4
addressed upfront versus during mid-deployment, in
order to have better control over the costs.
Strongly Strongly
No. The Change Management Role Agree Agree Neutral Disagree Disagre
Users invovement have been effective in achieving better
1
system quality, use and acceptance.
Enterprise-wide culture and structure change have been
managed, the mentality change from using reams of paper
2
to electronic media have been encouraged, and ERP
facilitates that.
Education and training have been sufficient thus users
3
have gained an appreciation of the utility of the system.
The required discipline have been improved through
4
indoctrination at meetings to address attitudinal changes.
The need for organizational commitment have been
5 sustain both at top and middle level management during
the implementation.
46
Strongly Strongly
No. The Project Management Role Agree Agree Neutral Disagree Disagre
The basic description of needs have been refined to a set of
1 specific institutional acceptance criteria at an early phase of the
project.
2 A dedicated and competent staff have maintained.
ERP project team have been a combination of business,
3
information technology, vendor, and consulting support.
The project has a well-defined plan/schedule for all the
activities involved in the ERP implementation, with an
4
appropriate allocation of budget and resources for these
activities.
There have been a good coordination and communication
5 among the implementation partners, the project team and the
whole organization.
The project leadership engender trust and avoid attrition and
6
unnecessary competition among members.
The scope management have been effective in scope definition
7
and subsequent scope control.
Leadership have been effective in leadership skills, respect of
8
project members and administration.
Strongly Strongly
No. ERP Implementation Success Agree Agree Neutral Disagree Disagre
The overall ERP implementation have been effective
1 regarding assuring the intended benefits can be realized
successfuly.
47
Annex 2 – Questionnaire for Package Leads and Core Team Members
Addis Ababa University
School of Commerce
Dear Respondents
The questionnaire is based on your experience and involvement in EEU's ERP implementation.
The questionnaire is designed to evaluate the success of the ERP implementation by selected five
management roles. The findings of the study will propose possible solutions to the challenges
and setbacks encountered during the implementations and denote lessons learned for future
endeavors.
Year of Experience 1.0-10 years 2.10-20 years 3.20-30 years 4. 30-40 years
48
As a member of Implementation Team and by applying the definitions provided for each
management roles, please provide your views:
Effective Top Management Role: The top management role includes clearly articulating goals
and vision, approving the correct ERP version, outlining implementation strategy, support in
cash and kind, delegate the decisions, and champion/advocate the project.
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
49
What recommendations do you have for future endeavors?___________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
50
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
51