Module CC3002 Post Implementation Issues Lecture for Week 7 AY 2013 Spring.

Module CC3002

Post Implementation IssuesLecture for Week 7

AY 2013 Spring

Post Implementation

Review

PIR

• What is PIR?• What does a PIR include?• Why conduct a PIR?• Project Failure• How PIR helps in future projects

What is PIR?

• A meeting that occurs after a system is operational…to review the success of the project• Months after project finishes–Not so long so that users forget–No too soon as users aren’t

sufficiently familiar with the system

Includes• Identification of faults and suggested

enhancements• Agreement on what needs to go in future

release• Success of project in terms of

budget/timescale• Success of system in meeting objective• Development practices that worked well

or badly

Software Metrics

Actual Development Time Against

Estimates For

All Development Activities

Software Metrics

• Accurate estimates are difficult to make• Using metrics from previous

projects can improve estimation purpose• Can measure quality of software• Errors/1000 lines of code - KLOC

Why conduct PIR?

• Project Manager and Development Team• .. Why care? Its over now !• Improve the process for next time

Why conduct PIR?

• Might include–Users involved during development–Managers of user department or

system owner–Steering Committee members–Facilitator

Why conduct PIR?

• Decide what more needs to be done–In future release software–To improve usage of new system

Why conduct PIR?

• Learn lessons for future projects• Formalize completion of project• Evaluate new IS–Was the project worthwhile–Did it deliver the

expected/sufficient benefits–Was the project a success?

Why do IT projects fail?

“Research suggests that between 50 to 70 percent of all system development

projects fail.”


28%

46%

26%

Sales

Fail to Complete Challenged by Time and CostCompleted


Such a Poor Record !

Why???

5 Reasons of Failure

• Technical Failure–Poor Technical Quality


• Data Failure–Poor Data Design–Processing Errors–Data Quality at Input–Poor User Procedures


• User Failure–Not using system to maximum

capability


• Organization Failure–System works but doesn’t meet

organization’s needs


• Failure in Business Environment–System not adaptable–System unable to cope with large

volume of transaction

Definition of IT Project Failure

• 4 views• Lyytinen and Hirscheim, 1987


• Correspondence Failure

IS delivered but doesn’t meet its original objectives


• Process Failure

Either development has not Produced a workable IS

ORProject runs over cost/time


• Interaction Failure

Heavily used – SuccessHardly used - Failure


• Expectation Failure

IS fails to meet a specific stakeholder’s expectations

More Reasons of IT Project Failure

10 Deadly SinsCollins and Bicknell, 1998


• Over Ambition

Trying to do too much


• Pride

Project Manager unwilling to admit ignorance


• Presumption

Belief that computerization is always a Good Thing !


• Lacking Courage and Resolution

Senior Managers unwilling to makeA key decision as they don’t know

about IT


• Credulity

Believing supplier’s promises


• Consultancy

Reliance on consultants who are charging big $$$$


• Tailored Software

Insisting on bespoke development Or Tailoring package solutions


• Concealment

Hiding Project Problems


• Buck Passing

Blame somebody else


• Lawyers

Believing they can sue the supplier if it goes wrong !

Tips for Project Managers

• Projects with realistic budgets and time table don’t get approved• Activity in early stages should be

dedicated to finding the correct question• The more desperate the situation,

the more optimistic is the progress report


• A user is a somebody who rejects a system because it’s what he asked for• Nothing is impossible for the

person who doesn’t have to do it


• Everyone wants a strong project manager – until they get it• The worst project managers sleep

at night• Projects don’t fail at the end, they

fail at conception


• Overly ambitious projects can never fail IF,

They have a beginningThey have middle processANDNO END !!

Summary

• Identify faults in system• Consider possible enhancements• Agree on features of future

release• Software metrics• Why projects fail?• Evaluate-Learn-Improve

Thanks Y

Thank You.

Module CC3002 Post Implementation Issues Lecture for Week 7 AY 2013 Spring.

Documents

Transcript of Module CC3002 Post Implementation Issues Lecture for Week 7 AY 2013 Spring.