“Houston, we have a problem” is one of the least desired messages one wants to receive when a multimillion solution is already launched into the space. And it´s in the hands of both module crew and mission control to handle the situation. Or rather avoid it happening and test the oxygen tank properly while still on Earth.
Just like shiny space vehicle, the S/4HANA transformation can open new horizons on the way to intelligent enterprise and enhanced productivity through increased business agility and real time data analysis. And not necessary a rocket science but definitely an appropriate quality assurance would contribute a lot.
What are the challenges?
Even if rocket science is not involved, the S/4HANA transformation still is a complex project or program with many stakeholders. Typically, such projects face issues in four dimensions:
• KPIs and effective project controls aligned with the chosen delivery methodology
• Change management both in the sense of people (user trainings, solution walkthroughs, etc.) and of control over emerging ad hoc changes
• Business process re-design, especially considering the new technical possibilities provided by HANA
• Communication, not only between different service providers but also internally among involved stakeholders
Overall, the problems in these areas lead to budget overruns, delays in project schedule and inconsistencies in solution scope which may result in bigger financial or reputational loses for a company.
Powerful tool, not a bottleneck.
The effective test management along with well-thought-out test strategy, helps to handle these challenges and, in the end, to secure the success of S/4HANA transformation:
• Testing as well as proper testing KPI creates transparency regarding the solution maturity, helps to measure it, identify the gaps, and assess the related risks.
• Testing is one of the classical risk mitigations means. With risk assessment techniques (e.g. workshop-based or supported with tools like BPCA or LiveCompare) the most-at-risk objects or processes are identified, and optimal test coverage defined which significantly reduces the overall business risk.
• The efficient testing (e.g. optimized test scope based on risk analysis and elimination of unnecessary testing, tailored degree of test automation, centralized test data management, earlier involvement of key users in testing) leads to the testing cost reduction and shorter hyper-care phase.
• Although testing should be clearly separated from the training phase, the involvement of the key users in the test activities in earlier stages help to better understand the solution which contributes to the overall change management as well and it can potentially reduce the number of requested changes later.
• Also, the considerately setup regression and smoke testing helps to better control the ad hoc changes, by ensuring that other critical functionalities are not damaged by a change. One of the fitting test methodology frameworks facilitating the regression test setup is represented by Sixsentix Software Agile Testing (SWAT) approach where SWAT team implements a self-contained Test Case Portfolio (a minimal and non-redundant set of test cases, achieving the highest possible test coverage with less effort in error analysis and maintenance) fully prepared for instant automated or manual execution.
Per aspera ad astra!