...
User testing is highly recommended in this regard. The test cases for user testing for the modular version can be found here: User interface test - openIMIS - Confluence (atlassian.net. However, based on the country customizations, some test cases may need adaptations. It is also advised that beyond these test cases to ask different user groups to also undertake free testing from their perspectives beyond such a structured test cases list, to allow for opportunities to test the system from the perspective of different eyes.
In case you find any issues during your testing process that the Initiative developers should rectify or enhance please report them to the openIMIS Service Desk.
Step 5: User training
The main difference between the legacy and the modular version, for from the point of view of the end user, is the interface. Indeed, colors, fonts, and certain tabs have changed and perhaps some features provide you with more flexibility which might also allow you to enhance your usage of openIMIS. So this would also be a good opportunity for you to review the way in which you are using openIMIS and in that regard also revise the way you want to train or rather retrain users on use of the new modular version of openIMIS. Therefore, an important step in the transition will be to conduct trainings to introduce different end users user groups to the new interfaces. This will also mean to consolidate consolidating and update updating all training material and other documentation beforehand. The following sub-steps have been identifiedhence are useful to have at hand:
Consolidate all existing material and documentation used for openIMIS
Update existing training material and reference manuals with new interfaces (slides with interface screenshots, user manuals, practical exercises etc.)
Organize Re-organize trainings for different group of actors
Step 6: Step by step introduction (pilot and then scale up)
Once the new modular version is ready to be rolled out and gone through you own teams testing process and subsequent trainning of respective user groups it would be advisable to introduce the system in steps to allow for a gradual transition. As per your implementation realities it is possible that a one time complete transition and roll out is a better approach. Generally speaking though it is useful as with any introduction of a new software, a new module or a prototype, to introduce the new solution in steps either geographically or by user groups or other categories that you might find as meaningful in your context. This would allow for gradual introduction and resolution of issues if they come up as well easier roll back that impacts lesser part of your operations in case of any major issues that you might observe.