c. Would you want the prototype to be operational or nonoperational? Why? If it were an
operational prototype, what would have to happen? If it were a nonoperational
prototype, how would the prototype be used?
The answer to these questions will vary depending on the student’s view of the situation.
Some of the points the student should bring up are:
Nonoperational Prototype.
d. Suppose the company decides the prototype system is not practical, abandons it, and takes
some other approach to solving its information problem. Does that mean prototype is not a valid
systems development approach? Explain your answer.
process.
21.8 Norcom, a division of a large manufacturer, needed a new distribution and customer service
system. The project was estimated to take 18 months and cost $5 million. The project team
consisted of 20 business and IT staff members. After two years, the CIO was fired, and the
company hired a CIO with expertise in saving troubled projects. The new CIO said three
grave errors were committed.
1. IT picked the wrong software using a very naïve request for proposal process.
2. IT did not formulate a project plan.
3. No one “owned” the project. The IT staff assumed the users owned the project, the users
believed the IT staff owned it, and management believed the vendor owned it.
The CIO developed a 2,000-line plan to rescue the project. Three months later, the system
failed, even with IT staff and consultants working on it day and night. The failed system was
to have been the company’s preeminent system, but it could not even process customer orders
correctly, resulting in complaints about late shipments and receiving the wrong goods.