1 / 7

IS Success/Failure

IS Success/Failure. Saonee Sarker. Information Systems Success Model (taken from Delone and McLean 1999). Information Quality. Intention to use. Use. System Quality. Net Benefits. User Satisfaction. Service Quality. Is INFORMATION SYSTEMS PROJECT Success and Failure the Same thing?.

randy
Download Presentation

IS Success/Failure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IS Success/Failure Saonee Sarker

  2. Information Systems Success Model (taken from Delone and McLean 1999) Information Quality Intention to use Use System Quality Net Benefits User Satisfaction Service Quality

  3. Is INFORMATION SYSTEMS PROJECT Success and Failure the Same thing?

  4. Types of IS Failures(taken from Lyytinen and Hirschheim 1999) • Correspondence Failure • Design objectives are stated earlier • When objectives/goals are not, it is a failure • Objectives can be well-defined and therefore can be measured accurately • Cost-benefit analysis and cost-accounting analysis often used

  5. Types of IS Failures (contd.) • Process Failure • When the development process fails to produce a workable product • When the process involves huge overspending in both cost and time. • Often reflects’ managers’ inability to achieve predicted resource allocations

  6. Types of IS Failures (contd.) • Interaction Failures • Low level of IS use can signal a failure • User attitudes are low, leading to low interaction with the system and hence poor improvements in performance

  7. Summary • Most IS projects are neither successes or failures, and receive mixed report cards • Important to conduct project retrospectives • Important to understand and analyze stakeholder satisfaction and expectations • Remember, expectations change frequently • One needs to monitor expectations continuously

More Related