Abstract
|
Organizations are generally expected to achieve significant benefits by selecting and adopting a robust information systems development methodology (ISDM). However, the study reported herein indicates that the extent of adoption of a methodology for IS development is quite inadequate. As different types of systems may require different types of tools, techniques, software processes and programming paradigms, no single set of solutions is best for all situations. When considering the adoption of a systems development methodology, management must take into account the industry, organization, projects, system products and individual developers involved. This paper provides an overview of the typical components of such a methodology, relates the components to the various stages of adoption, and examines the reasons for adopting or not adopting a methodology. Finally, based on the empirical findings, a framework is proposed to help management make informed decisions regarding the adoption and implementation of methodologies that can meet the specific IS development needs of their organization.
|