2. Agenda
• Project Overview
• Feedback after implementation
• Failure Analysis
• Root Cause Analysis
• Learning from failure
2
3. Project Overview
Project Preparation Realization
Monitor
Initiation Planning Execution & Closing
Control
Project Start: 22/01/2009
Project End: 04/11/2009
Business Blue Print ‘Go Live’
Project scope Business Process Setting up QA
was to was mapped (Testing) and PD
implement ERP and blueprint (Production)
using a standard was submitted ; environment.
s/w with limited It was signed-off Configuration of ERP
customization by the users system with master
data received from
Accounting, Inventory Management functional / power
and Billing were part of the scope users. Completion of
training manual.
Estimation of work: Base modules of Training the users;
the ERP package and 100+ programs Communication to
for customized functions. them about transition
Estimated duration: ~40 weeks to new system
Project was completed ahead of schedule! 3
4. Feedback after Implementation
922 issues were raised by the users in the period of 12 months after ‘Go Live’
User Query Clarification 484
User Authorization 68
Statutory Enhancement 2
Major Enhancement 20
Minor Enhancement 161
Master Data reconfiguration 87
System related bug 100
0 100 200 300 400 500 600
4
5. Failure Analysis
High
Minor 163 20
Impact on Project Cost
enhancement; Major
Statutory enhancements
enhancements
Master Data User
configuration; authorization;
System related User clarification
bugs 187 552
Issue type by Severity
Low
Low High
1. ~ 60% of these issues were attributed to access & inadequate training
2. ~ 20% of these issues were related to bugs & master data
3. ~ 17% of these issues were related to minor changes
4. ~ 3% of these issues were major changes & high cost of the project 5
6. Root Cause Analysis
People Process Diminished
confidence
68 users missing User discontent in the system
87 Master Rework on
Data issues Master data
484 Queries Need
for more
help desk 100 system Poor quality of
staff Related bugs testing
Project
Failure
161 Minor
enhancements Poor Project
Definition
No visible negative
impact from 2 statutory Lack of
technology provider / enhancements involvement
vendors 20 Major of key users ?
enhancements Increased cost
External Unknowns 6
7. Learning from failure
Project would not have got into trouble, if following were
taken care of
Involvement of all users
User training and training manuals
Engaging subject matter expert (SME) and
key users for business process definitions
Educating the users on master data
Involvement of focused user groups for
testing the system prior to ‘Go Live’
7
8. Project Preparation Realization Learning from failure
& Business Blueprint & ‘Go Live’
Initiation & Planning Execution, Monitor & Control Diminished
confidence
Ambiguous Inadequate resource in the project
Project Definition Identification
Weak PM discipline Discontent amongst
Lack of Project team
details Project
Delay
User discontent Rework, Increased project
Competing needs New work, Reschedule cost
of stakeholders Project
Failure
Wrong technology / Poor Risk Planning ? Poor risk
Vendor selection ? Mitigation
Solution not
Meeting the needs
These are some of the
reasons for failure of a
project
External Unknowns 8
