Why can't we implement this SDM?

To cope with the mounting demands for large, complex information system applications, most organizations turn to a systems development methodology. SDMs are logically appealing, offering a flexible framework for the sequence of tasks needed to develop an application, as well as tools and techniques for accomplishing these tasks. By creating an engineering-like development discipline, SDMs provide explicit deliverables and consistency as information systems are built. In its intent, an SDM should reduce the risk associated with shortcuts and mistakes and ensure that quality infuses the software process. On the surface, at least, it would seem that every organization should have an SDM in place. Unfortunately, most IS organizations fail to successfully implement and utilize an SDM. The question is, why?. © 1999 IEEE