Choosing Agile or Plan-driven Enterprise Resource Planning (ERP) Implementations - A study on 21 Implementations from 20 Companies

Lucas Gren, Alexander Wong, Erik Kristoffersson

Abstract

Enterprise Resource Planning (ERP) implementations are high-stakes projects traditionally managed through plan-driven, "Waterfall" methodologies. However, increasing market volatility has led many organizations to consider Agile approaches. This study examines 21 SAP implementation projects across 20 companies to determine if strategic decision-makers can effectively distinguish between projects suited for Agile versus those suited for plan-driven methods. The results indicate that for "middle-ground" projects, the two methodologies are often indistinguishable at the strategic level. Furthermore, the choice of Agile is frequently driven by dissatisfaction with legacy processes and a prioritized focus on cost reduction, rather than a project's inherent suitability for iterative development.

Introduction

Enterprise Resource Planning (ERP) systems serve as the operational backbone for modern enterprises, yet their implementation remains notoriously difficult and prone to failure. Historically, these projects have relied on plan-driven methods characterized by extensive documentation and high predictability. As business environments become more volatile, the industry has seen a push toward Agile methodologies.

The fundamental differences between these two paradigms are stark, as summarized in the table below:

Comparison of Traditional and Agile development methodologies

Despite these clear conceptual differences, managers must often decide on a methodology at a very early, strategic stage. This research investigates whether decision-makers possess sufficient information to make an informed choice or if they are effectively "flying blind" when selecting between Agile and plan-driven frameworks for ERP deployments.

Methodology

The researchers synthesized three established "Agile Fit" frameworks—Datta’s Agility Measurement Index, Boehm & Turner’s Risk Scales, and Sidky’s Agile Adoption Framework—into a comprehensive 29-item survey.

The study focused on "design-based" SAP projects that occupy a middle ground between purely repetitive and highly experimental work. The dataset comprised 21 projects from 20 diverse companies across North America, Europe, Latin America, and the Asia-Pacific region. Given the specialized nature of the sample—which included nearly the entire known global population of Agile SAP implementations at the time—non-parametric statistical tests (Fisher’s Exact Test and the Mann-Whitney U Test) were employed to analyze differences in perception between Agile and plan-driven project managers.

Key Findings

The "Middle Ground" Muddle

The study found that for projects that are neither extremely stable nor wildly innovative, decision-makers cannot reliably distinguish between Agile and plan-driven fits. On nearly every metric, including project complexity and team stability, the two groups appeared identical at the project's inception. This suggests a significant gap in the strategic information available during the methodology selection phase.

Agile as a Reactive Choice

A significant finding was that the adoption of Agile was often a reaction to past failures. Agile projects were preceded by a high degree of discontent with previous implementation methods ($p = 0.035$). Companies appear to turn to Agile as a "Hail Mary" when their current processes are deemed insufficient, rather than selecting it based on project-specific technical requirements.

The Cost Fallacy

In the studied sample, there was a 100% correlation between the selection of Agile and the prioritization of "low cost" as the primary project driver (ahead of Quality and Time). This is paradoxical, as the authors note that Agile's primary goal is value and satisfaction, and its steep learning curve can often lead to higher initial costs compared to traditional methods.

Executive Buy-in and Process Change

Agile projects exhibited higher levels of executive buy-in specifically regarding "process change." This reinforces the notion that Agile is often chosen when leadership is desperate for a fundamental shift in how the organization operates, regardless of whether the specific ERP project is a natural fit for Agile.

Conclusion

The research highlights a critical "contextual blindness" at the strategic level of ERP planning. Managers often lack the granular knowledge—such as specific team capabilities or local organizational culture—required to choose the most effective methodology. As most modern ERP projects evolve into "hybrid" models (often termed "Water-Scrum-Fall"), there is an urgent need for better tools to manage the unique risks associated with blending these two disparate worlds. Future research should expand beyond the SAP domain to determine if these findings hold true across broader software implementation landscapes.

Summary updated

Abstract

Agile methods have gotten a good reputation for managing projects in many different sectors. A challenge among practitioners in the ERP (Enterprise Resource Planning) domain, is to decide if an agile method is suitable or not for new projects. This study investigates how decision-makers select between agile and plan-driven ERP implementation projects in relation to known factors from previous research. We selected projects that the decision-makers assessed as successful, but borderline, agile and plan-driven projects already implemented and let project managers fill out a survey consisting of key agile or plan-driven characteristics. We found that the assessment made by decision-makers did not differ on any aspects except higher executive buy-in for process change, and the prioritization of low cost in the agile projects. This study highlights the difficulty in selecting implementation strategy for a large part of the ERP implementations, and the data show that the decision-makers could not make such a decision at an early point in time without contextual knowledge.
BibTeX
@inproceedings{gren2018choosing,
  author = {Lucas Gren and Alexander Wong and Erik Kristoffersson},
  title = {{Choosing Agile or Plan-driven Enterprise Resource Planning (ERP) Implementations - A study on 21 Implementations from 20 Companies}},
  booktitle = {STPIS@CAiSE},
  year = {2018},
  url = {https://openreview.net/forum?id=VQWGZkENdbPp},
}
Figure