Abstract
Enterprise Resource Planning (ERP) implementations are complex, high-stakes projects that traditionally rely on plan-driven methodologies. As Agile methods gain popularity, decision-makers face the challenge of selecting the most appropriate approach. This study investigates 21 successful ERP implementations to determine if strategic characteristics can distinguish between "Agile" and "Plan-driven" projects at their inception. The findings suggest that at the strategic level, these projects appear nearly identical, with the choice of Agile often driven by a desire for cost control and a reaction to previous process failures rather than objective project traits.
Introduction
ERP implementations, such as those involving SAP, are the "heavy lifting" of the IT world. They are enterprise-wide, highly integrated, and require significant architectural planning. Historically, the stability of these systems favored the "waterfall" or plan-driven approach. However, the "Agile" wave has reached the ERP domain, leaving managers to decide: stick to the plan or embrace the pivot?
The Theoretical Divide
To understand the choice, one must first look at the fundamental differences between the two methodologies. Traditional approaches assume systems are fully specifiable and predictable, while Agile assumes that high-quality software is best developed through continuous improvement and rapid feedback.
As shown in the table above, the two paths differ across management styles, communication, and project cycles. While researchers have proposed various "Agile Fit" tools based on these characteristics, there has been little empirical evidence showing whether these factors actually guide successful real-world selection.
Research Methodology
A study by Lucas Gren and colleagues synthesized three existing "Agile Fit" frameworks into a comprehensive survey. They targeted 21 successful ERP implementation projects across 20 companies globally, including North America, Europe, Latin America, and Asia-Pacific.
The researchers focused on "design-based" projects—those where the choice of methodology is not immediately obvious. Project managers assessed their projects on 29 items, including project novelty, prioritization (Time vs. Quality vs. Cost), and executive support. Statistical analyses, including Fisher’s Exact Test and the Mann-Whitney U Test, were used to identify significant differences between the agile and plan-driven groups.
Key Insights and Results
The "Middle Ground" Fog
For projects in the middle of the spectrum—neither extremely stable nor purely experimental—there were almost no strategic differences. Standard metrics for choosing Agile, such as the "Rate of Change of Requirements" or "Project Novelty," showed no significant difference between the two groups. On paper, an agile project looked just like a waterfall project at the strategic starting line.
Agility as a Reaction
The study found that the most significant reason companies chose an agile approach was dissatisfaction with their current process. Agile projects had a significantly higher mean rank for having an "insufficient current development process" (12.79 vs. 7.41 for plan-driven, $p = 0.035$). If a previous waterfall project failed, the next was more likely to be labeled "Agile."
The Cost Paradox
In the agile projects studied, Cost was the top priority, even over Quality and Time. There was a 100% chance in this sample that an agile project would prioritize cost first (rejected null hypothesis with 94.2% probability). This is counterintuitive, as Agile is typically associated with value and flexibility. The authors suggest this is due to the commercial setup: while waterfall projects are often fixed-price, the "pay as you deliver" nature of Agile requires tighter, active cost control.
Conclusion
Decision-makers often lack the deep contextual knowledge required at the start of a project to make a truly informed methodology choice based on objective characteristics. Instead, the shift toward Agile in the ERP space appears to be driven by organizational "vibes," a desire for better cost management, and a reaction to the perceived failures of traditional bureaucratic structures. For practitioners, the takeaway is clear: ensuring success requires moving beyond surface-level labels to understand the specific contextual needs of the implementation.
Summary updated