Which statement best describes when to use Agile vs Waterfall in ERP implementation?

• A. Waterfall is best for evolving requirements and frequent client feedback
• B. Agile should be used when requirements are evolving and client feedback is frequent
• C. Hybrid approaches are never appropriate
• D. Waterfall should always be used for fixed scope projects

Answer: (B)

The main idea being tested is how to choose a project approach based on how stable the requirements are and how much client feedback is expected. In ERP implementations, when requirements are evolving and the client needs frequent input, an Agile approach fits best because it uses short iterations, regular demos, and continual reprioritization. This allows the team to adapt to changing processes and integrations without locking in a rigid, long upfront plan.

Waterfall, in contrast, assumes a well-defined set of requirements from the start and proceeds in a linear sequence. It tends to slow down when changes arise, which is common in ERP projects as you uncover new needs after implementation begins. Hybrid approaches can be effective too, blending fixed-scope portions with flexible, iterative work.

So the statement that Agile should be used when requirements are evolving and client feedback is frequent best captures when Agile is the most suitable choice.