Planning for a successful Dynamics 365 Quality Engineering programme
Too often, companies are firefighting quality issues that have not been budgeted for. A better approach is to assess the total cost of ownership of quality processes and then work on optimising that.
Regulated businesses are ahead of the curve. Because of stringent compliance requirements for quality, regulated businesses plan for quality assurance and budget allocation from the beginning. It is time for this approach to be adopted more widely if D365 is to deliver quality enterprise support.
Watch the video to hear the insights shared from our Testhouse experts and clients
What are the key characteristics of a successful D365 journey?
Building in quality from the beginning is the key characteristics of a successful D365 journey. Steve Williams says: “It's taking the time at the start to plan well, and not rush headlong into delivery. And making sure testing and quality is embedded all the way through the thinking of the program.”
Testing early should be number one priority, according to Sug Sahadevan: “I would strongly advise people to use automation and where they have used test automation, they have been extremely successful. Not only in terms of finding the bugs early, but also the speed of the project.”
Jermy Jose says: “The key characteristics for successful D365 journey have been early engagement of QA, to ensure that user end stories and acceptance criteria are complete and accurate. Then the second point is accurate impact analysis, so identifying what is required to be tested, based on what is impacted.”
How do you identify and manage the impact of regular updates from Microsoft?
A Testhouse survey revealed that 66% of respondents do not test their D365 after an update and that they had not thought of QA for D365. Almost everyone (99%) agreed that implementing QA could provide a 90% reduction in production issues and a 70% increase in product efficiency through independent verification and validation.
Watch the video to hear the insights shared from our Testhouse experts and clients
Steve Williams debunks the myth that user acceptance testing (UAT) will largely pick up any issues. He says: “If you have integrations with other legacy systems then you're going to not pick those things up in UAT, they move straight away through the food chain through delivery. And you only find those things in production, when your users are raising support tickets.”
"It's always best to think about the quality planning upfront, making sure it's robust, making sure you've got the right people with the right experience undertaking the testing.”
Steve Williams
CRM Programme Manager BARRATT HOMES
