SESSION GOAL:  After completing this session you should be able to identify factors that lead to project escalation and development failures. You should also be able to develop an audit plan that would detect potential development problems.

• Read Oz, E. 1994. When professional standards are lax: The CONFIRM failure and its lessons. Communications of the ACM 37(10), 29-36. YTou will need to click on the PDF icon to download the article.
• Read Stanford, The project from hell, Computerworld, September 4, 1995.
• Skim Keil & Mann, The Nature and Extent of IT Project Escalation: Part I, IS Audit and Control Journal in the COURSE MATERIALS section of Blackboard.
• Skim Keil & Mann, The Nature and Extent of IT Project Escalation: Part II, IS Audit and Control Journal in the COURSE MATERIALS section of Blackboard.
• After the discussion, go to the COURSE MATERIALS section of Blackboard and read Tomsho, R. 1994. "How Greyhound Lines re-engineered itself right into a deep hole," The Wall Street Journal (10/20): A1, A6. Prepare an audit plan that, if executed in a timely fashion, would have detected the system development and execution flaws soon enough for Greyhound to have avoided them. To minimize the likelihood of failing to identify all the unsuccessful systems development practices, start by making a list of them. Then develop an audit plan that addresses each one. This audit plan is an INDIVIDUAL assignment and is due at the beginning of class on July 14..