1. Lecture Overview
IT System Failures

2. IT kills patients
patients-at-risk-ama-says/ ?section=vic

3. Lessons learnt can secure Future Performance
Who learns from IT system failures
All project team members
Project managers learn about PM failure drivers
Other team members learn about SLDC and software engineering shortfalls
All better identify future risks from the various problems they face while executing mgt & dev work
Business users can learn about business/ICT integration shortfalls
Why bother with such learnings?
Required as part of committing to:
A continuous quality improving work culture
A risk management work culture as future risks can be identified from past problems and failures (the impacts of risk occurrences)
Foster organisation learning and capability maturity development
Supports a program logic work culture in ensuring high success in:
Projects to deliver strategies & business plans
Ops to deliver products and services most efficaciously, hence contributing to maximising the bottom lines
Lessons learnt can secure Future Performance

4. Concepts for identifying causes
3 Framework models
Classification of IT project failures

5. Using 3 Frameworks to ID System Failure Risks or explain the causes of past & existing system failures
Cultural, Managerial & Technical (CMT) Causes
Stakeholder relationships & power-plays
3D predictive modelling of CMT factors

6. IT System Failures – Types & Causes
Communication issues
Process flow issues
Relationship & interaction issues – people to people, people / machine

7. IT System Failures – Types & Causes
Poor project management performance:
Budgets
Timelines
Scope control
Other PM issues

8. IT System Failures – Types & Causes
Poor coordination
Poor information sharing
Poor trust in project or resisting or fearing change associated with projects
Inter BU rivalry
Anything else that causes user dissatisfaction

9. Cause - Effects
Cause

10. Tutorial Section B: Discussion questions (Group activity)
B1) What is the meant by correspondence failure for IT systems failure context? How can this type of failure be avoided? Discuss.
B2) Can an IT systems failure be classified into more than one category? Present your arguments.
Section C: A mini-case (Group activity)
Please carefully read the case report on e-procurement project failure, and discuss the following questions:
Discussion Questions
C1) Who are the stakeholders?
C2) Why did not the procurement manager conduct a proper stakeholder identification analysis?
C3) Why did the procurement manager fail to consider suppliers as an important stakeholder?
C4) How did the suppliers contribute to the project abandonment?
C5) Was there an alignment between the objective of introducing E-PRO and that of the suppliers?
C6) Did the support of any stakeholder change for the project?

11. Portfolio Assignment 1 – Part 2
Most IT professionals assume that evaluating IT success or failure is not their job. Do you agree with this argument?
Present your arguments.
Add the arguments to your tutorial portfolio (Part D) in a document and submit the portfolio (via Moodle) in Week 12.