Each methodology has both strengths and weaknesses, and no one size fits all in the ERP world. Hence, the project team should carefully evaluate the best-fitting methodology to achieve the business goal.
No one size will fit all situations; however, for easing your effort in choosing a methodology, we are sharing a comparative summary of the key attributes of the preceding methodologies:
| Attribute/Scenario | CRP | Agile | Waterfall |
|
End-to-end greenfield implementation of Microsoft Dynamics 365 for Finance and Operations |
This is the latest and most widely used methodology in modern digital cloud initiatives. This blends the agile and waterfall approach to achieve the project goal. |
Though this could be used, a lot of project management efforts will be needed, as it will not be able to handle all of the ambiguities that come with an ERP implementation. This is a good one to leverage with highly evolving solution needs. |
The traditional approach, which is still OK to use, but the duration of the project is typically longer before you can start reaping benefits. Good for a known set of business needs and smaller time frame initiatives. |
|
Enhancements and new feature implementations |
This is very well suited to these initiatives. |
Depending upon the delivery duration, clarity of requirements, and technical design, this methodology can be used. |
Typically, this one is not used for a shorter duration due to the huge efforts involved. |
|
Upgrades/migration |
This is very well suited to these initiatives. |
This methodology may be used in upgrades and has significant overlaps with the CRP methodology. |
This methodology could be used; however, for faster ROI and buy-in from end users, either CRP or agile is preferred. |
|
Support/maintenance |
This is very well suited to these initiatives. |
This methodology overlaps with the CRP methodology and is suited for support. |
Typically, this one is not used for support. |
What has worked for us is the CRP methodology, as modern ERP is no longer a traditional application, hence the traditional approach of waterfall is not the best fit. Agile is second in our list when the number of moving parts is high and when the project structure needs to be highly adaptable to changing business needs.
In the next section, we'll share the importance and best practices in project initiation.