Comparative summary 

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 the situations; however, for easing your effort in a methodology, we are sharing a comparative summary of the key attributes of the preceding methodologies:

Attribute/methodology CRP Agile Waterfall

End-to-end greenfield implementation of Dynamics 365 for Finance and Operations, Enterprise edition or Business edition

This is the latest and most recommended methodology from Microsoft in this modern digital cloud era

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

Traditional approach, which is still OK to use, but the duration of the project is typically longer before one can start reaping benefits

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 could have 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 suited for support

Typically, this one is not used for a shorter duration due to the huge efforts involved

 

What has worked for us is the CRP methodology while implementing and embracing Dynamics 365 solutions. As your new ERP is no longer a traditional application, the traditional approach of waterfall may not be the best fit, while agile is not intended for long-running initiatives. Hence, it is also carefully used, based on the situation.

Microsoft Dynamics 365 has created a new trend--customers are implementing multiple Dynamics 365 products, such as Sales and Finance, and Operations, Enterprise editions together. There may be two different teams implementing these two product lines. However, it is critical for these teams to collaborate with each other and align their methodologies for a smooth implementation and roll-out of each product. 

After selecting the methodology and project implementation strategy, let's look at the tool sets available to help your implementation project. Microsoft LCS combines all the tools you will need throughout your project lifecycle. The next section provides an overview of LCS, and all the tools available and their use.    

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset