Identify the technical gaps

Completed

The ability to understand the gaps in functionality between the old and new systems is important for planning the design, to help determine new functionality and establish how and when it can be deployed.

For example, if the business creates and posts many sales orders, and the process that is currently in use requires extensive functionality changes within Dynamics 365 Supply Chain Management, you must determine if you want to keep the same process or make modifications to it. When that has been determined, you can focus on whether it might be more pertinent to discuss how the system functions out of the box and how a few changes can enhance the process instead of conforming to dated and inefficient practices. In other situations, it might be worth it to expend the effort and make more customizations to the system for the previous process if it will enhance the overall workflow.

When considering desired functionality, you should keep in mind the level of effort that is needed and the timeline of the project to ensure that the overall implementation is considered.

Identify the development requirements for the solution

After you have determined the gaps between the current and desired functionality and the new features that are to be implemented, it is important to identify the specific development requirements for each of the solutions. You will need to address and understand the impacts of each solution as you identify the requirements to ensure quality planning and a smooth implementation.