We often choose one way over that other.
There are thousands of blog posts, books that suggests choosing one implementation method/framework over the other.
I believe each implementation method/framework has its strengths. The value is in evaluating which method suits the best for a given task, stakeholders, and environment?
Why can’t we apply Agile, Waterfall and Critical Chain together in a given ERP project?
For repetitive, simpler tasks like Infrastructure Analysis, ERP Software installation, Data Migration, Training, simple customisations etc. we implement Waterfall.
For complex tasks like complex integrations, business process re-engineering along with complex customisations we apply Agile methods (like Scrum).
For all the overall project, we use Critical Chain Project Management. We remove buffers from the individual tasks and manage buffers separately. We limit Work in Progress (WIP). We focus on removing resource, task constraints. Overall, we try to increase efficiency of the project delivery.
The point is that the above methods can be implemented together. The challenge is to educate project team and stakeholders that these methods/frameworks can co-exist in a project.
We should not prefer one method over the other. I believe, this is holding us back. The fact is that Agile, Waterfall and Critical Chain can all co-exist and deliver excellent value to your ERP project.
What has been your experience? Drop me a comment.