Transcript Successful IT Implementations

Successful IT
Implementations
34% of projects
completed on time, on
budget, and with all specified
features and functions
Expectations on Project
Time Spent & Time Saved
 Cost and Revenue Increase
 Functionality (existing & future needs)
 Intangibles

 Learning
(Staff & Management Skills)
 Infrastructure (Standards, tools & shared info)
 Adaptability (Problem Solving & Resources)
 Org. Changes (Image, structures & comm.)
eBPLS Implementations

31 sites: Success Rate? Value Achieved?

How could it be improved?

What about other 69 municipalities?
eRPTS
Guidelines for implementation (PAU)
 Building upon eBPLS
 Data loading challenge
 Quality of system?
 CESO involvement?
 Project Management

Recommendations
Assign Project Sponsor (Sr. LGU Mgr)
 Assign Project Manager & Team with roles
 Monitor Progress (simple but written)
 Provide Ongoing Support (Internal & External)
 Promote Alignment with LGU Goals/Needs
 Evaluate Mid-term & Final for learning
 Recognize Team [informal & formal]
Is an approved Terms of Reference (SOW) useful?

Summary
“Success of a project will depend critically upon
the effort, care and skill you apply in its initial
planning.”
What about
1. Project Manager knowledge & skills?
2. Project Sponsor scrutiny & support?
3. Quality/Value of system being implemented?
4. Culture, Expectations, & Attitude of staff?
Terms of Reference (TOR)
aka Statement of Work (SOW)
Scope, Goals & Objectives of Project
 Schedule & Key Milestones
 Cost (Money & Staff Time)
 Project Organization & Staff Assigned
 Monitoring & Evaluation
 Issues & Mitigation Approach
 Change Procedures (are these needed?)

Progress Report
for MMM-dd to MMM-dd (2 weeks?)

Accomplishments in this period

Plans for next period

Key Issues & Approach to resolve (max 3)
(prepared by Project Manager
for Sponsor referring to Project Plan)
Project Risks
Misunderstanding on Scope & Objectives
 No Committed Project Sponsor
 Project Manager Lacks Skills
 New Technology Lacking Support
 Excessive Reliance on Tools
 Data Quality not Addressed
 Too Big a Step Forced on Users
 Security Issues Ignored
 No Monitoring nor Follow-up for Learning

Some Success Factors
Top management involvement
 Linking to previous successes
 Perceived low risk of implementation
 Low cost of implementation
 Focuses on a critical factor necessary for
the organization's success
 Lots of involvement of staff, crossdepartmental
 Hoopla, catchy name, fun, visibility, etc.
