There Is Still No "Fit for All" IS Development Method: Business Development Context and IS Development Characteristics Need to Match

Abstract

Information systems development has returned to strategic management due to the increase of softwareenabled businesses. We investigated two failed IS development projects using the exploratory case study method. One of the projects was executed with the plan-driven approach methods and the other with the change-driven (agile) approach methods. Data analysis showed that both projects followed the principles of the selected methods. That, however, was not enough. The plan-driven project achieved project objectives but did not deliver business value and the IS was never taken into use. The change-driven project delivered desired business value but failed to release a robust IS. Our main contribution to research is our proposition to match the characteristics of IS development methods with the characteristics of business development contexts. We also disclose some novel reasons for IS project failures.

On Solving the Business Requirements Engineering Problems of Information Systems Development Projects – Lessons from Three Projects

“…In our prior studies, we have shown the need to match the characteristics of ISD and BPD (methods) [8,22]. We reported the way in which matching deepens understanding regarding the findings of prior research, adds new insights, and helps practitioners to execute ISD (sub-)projects more successfully.…”

“…The ISD project failed. In these situations, requirements have changed entirely, making the IS obsolete [13,39] and/or changes to business (processes) have been neglected in RE [8].…”

“…On the other hand, some recent studies report that solving the inflexibility challenge inherent in plan-driven methods has created new types of problems. For example, the scope and the requirements of an ISD project may grow or explode uncontrollably leading to technical instability, scaling and other performance problems, technical debt and/or to business process instabilities [8,16,30]. Consequently, rigorous RE is still needed.…”

“…An ISD project is often a sub-project within a business development project together with a business process development (BPD) sub-project. The methods of ISD and BPD differ as do the professional backgrounds of typical IS and BP developers [8]. An organization could have independent ISD and BPD project teams, even within a single business development project.…”

“…An organization could have independent ISD and BPD project teams, even within a single business development project. The comparison of related ISD and BPD sub-projects' requirements specifications could be the only discussion issue between the two sub-projects [8]. The synchronizing of project deliverables and time-tables during later project phases seldom results in shared re-engineering of or changes to sub-project requirements [8].…”