By Deepesh Somani
One of the key challenges in Microsoft Dynamics is the process of managing the software development lifecycle well over different stages of the project and different kinds of Microsoft Dynamics projects. Let us go through this and try to understand some of the key aspects of managing Microsoft Dynamics 365.
It is a key metric in the software world that the majority of CRM and ERP projects fail. There are lots of reasons to attribute to project failure, but don’t you think as a Dynamics 365 professional that a lot of it is to do with the way Dynamics 365 projects are being implemented?
Here are some key areas that need to be considered ahead of time to manage a successful Dynamics 365 implementation:
With an array of Dynamics 365 product offerings from Microsoft, it’s always important to be on top of the knowledge game in terms of the Dynamics 365 product family. With the Power Platform also coming into play, it becomes even more important.
Often, the business needs of an organization are not mapped into the right product feature, or excessive customizations are made to the product. This creates a technical debt, which should be avoided at all costs and can unnecessarily increase the implementation time and cost of a Dynamics 365 implementation. Fit Gap Analysis early on in an implementation can help bridge the gap correctly.
Skillsets have always been a big challenge within Dynamics 365 implementations and projects. It takes a lot of skill to be experienced in the product domain as a consultant or a Microsoft Partner, so choosing an experienced partner is key to a successful Dynamics 365 implementation.
A lot of Dynamics 365 implementations forget to focus on the fact that user adoption and training are the key to success. Initially, the training involves basic sessions to impart knowledge on the product (I’d suggest this is done before requirements gathering).
In User Acceptance Testing, training involves identifying the right champions or ‘power users’, who will help train the others and also play an active role in getting the product to correctly suit the needs of the business. Most Dynamics 365 implementations fail at user adoption, so a training plan should be devised at the project deliverables stage to encourage eventual user adoption.
Traditionally, Dynamics 365 implementations used to be powered by Sure Step methodology from Microsoft. Over time, Agile approach has taken over. Deciding the number of sprints and duration is pretty important. Often, times users are not well aware of the actual use of Agile with Dynamics 365—experienced architects or project managers need to explain the right software methodology at the start of the implementation.
Dynamics 365 systems are often integrated with a lot of back end, internal and external systems. At times, initial implementation involves moving over from an existing system. Integration and migration design and approach thus play a very crucial role in a Dynamics 365 implementation, and that is what we will go through in the coming sections.
Check out our latest Microsoft technology job roles and make your move.
As I already mentioned towards the end of the last section, more often than not there is an existing application or set of applications managing the customer business. Dynamics 365 implementations thus involve migration of data from this line of business applications and moving them to a Dynamics 365 product. Here are some of the considerations one should keep in mind to manage a Dynamics 365 migration successfully.
Data quality is a key consideration when migrating it into Dynamics 365. In case data has been stored in an existing application over the years, some of the relevant questions to consider are:
Data migration is often lacking enough time spent on design. Considering it is only a one-time activity, it is rarely given enough think time on the design board or a proof of concept to validate the outcomes. This is a big risk to a Dynamics 365 implementation. Some of the challenges one can later see in the project, where not enough thought process has been put into your Dynamics 365 project, are:
Just like Dynamics 365, data migration also requires its own specific skillset. Often a Dynamics 365 consultant is also seen playing the role of a data migration expert. This might not be the best-suited approach for data migration, considering all of the best practices and approaches a data migration expert will bring.
Often, implementations fail and people spend too much time trying to re-invent the wheel when there are already proven tools, solutions and approaches provided by Microsoft, as well as partners, to speed up the data migration effort for a Dynamics 365 implementation. Using the right tool can greatly enhance the ability of migration required for a Dynamics 365 implementation.
As far as the online version of the product family is concerned, Dynamics 365 has been growing thanks to a rigorous set of upgrades. One of the key asks is utilizing the latest and greatest for you or your customer’s business in the best possible way. Some of the considerations for managing product upgrades successfully are:
I hope you found this article useful, and hopefully it will help you on your Dynamics 365 and Power Platform journey.
Deepesh Somani is a Practice Director for Customer Engagement and Power Platform at Dynamisity and a Microsoft Certified trainer. He has been implementing Microsoft Dynamics for the last 12 years, has been a Microsoft Business applications MVP awardee since 2015, and was recognized as one of the top 50 CRM bloggers in 2019 by Feedspot. You can find his blog by clicking here.
Fill out the form below and download a copy of the full Microsoft Dynamics Salary Survey report, including more information about the Dynamics market and salary data from thousands of professionals around the world.
Zapisz się, aby otrzymywać wskazówki Microsoft Azure i Dynamics