Implementation methodologies comparison for Microsoft Dynamics 365 Finance and Operations one version D365FO
Implementation methodologies comparison for Microsoft Dynamics 365 Finance and Operations one version D365FO
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 agile and waterfall approach to achieve 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 the ambiguities that come with an ERP implementation. Good one to leverage in a highly evolving solution needs. |
Traditional approach, which is still OK to use, but the duration of the project is typically longer before one can start reaping benefits. Good for known set of business needs and smaller time frame initiatives. |
Enhancements and new feature implementations |
Very well-suited to these initiatives |
Depending upon the delivery duration and 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 |
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 should be preferred. |
Support/maintenance |
Very well-suited to these initiatives |
This methodology overlaps with the CRP methodology and is also suited for support. |
Typically, this one is not used for support. |
*This post is locked for comments