Tips for D365 implementation and lessons learned
By following best practices for testing and quality assurance in Dynamics 365, organizations can reduce the likelihood of errors or defects in the system, which can improve user satisfaction and productivity, and ultimately lead to cost savings. Additionally, following best practices can help organisations stay in compliance with industry regulations and standards.
Watch the video to hear the insights shared from our Testhouse experts and clients
What advice can you offer when configuring and customising the platform?
There is a temptation for businesses to think they have unique and specific processes and challenges. That is rarely the case. The key to quality is to minimise customisation and fit the process around D365 as much as possible, rather than change D365 to fit the processes that you have.
How do you ensure your workflows all run smoothly when integrating between multiple systems?
Sug Sahadevan points out that MS D365 undergoes stringent testing before it leaves Microsoft, so potential weak points are much more likely to be where D365 meets internal systems. ”Performance could be perfect on D365 but the response from something else might be pretty slow, and that might cause a whole system to be performance-wise a little bit slower.”
Watch the video to hear the insights shared from our Testhouse experts and clients
The more you move away from the core product, the more issues you're going to store up, according to Steve Williams. He says: “I always use a rule of thumb on a Dynamics implementation that you never want to customise more than around 10% of the overall build.”
"When we get into our QA approach with the customer, we focus on the integration points.”
Jermy Jose Director - Delivery Excellence and Innovations TESTHOUSE
