Our Method To Avoid Madness
The ZUI project methodology is closely aligned to SAP ASAP methodology. For those familiar not familiar with this approach - a project is broken down into 5 key stages the ZUI process follows the same basic framework:
- Project Planning: A preparation workshop ahead of the official project launch. Typical outputs would be:
- Project governance
- Roles and staffing
- Issue identification and resolution
-
Blueprinting: A key stage of the project, where the inputs of project requirements are collected, analyzed and put into an output document that describes how the requirements will be turned into a solution.
What is clearly unique in the ZUI approach is that both a back end technical solution and a wire frame of the user experience and interfaces will be included at this stage.
Design and Build: In this phase the ABAP type back-end system team gets to work. The difference here is that by using the ZUI Application Framework, our team can standardize the way we get to the data logic which makes it: - Faster
- More reliable and stable
- Additionally we are also rapidly moving into fully designed front end screens for look and feel, discussing key aspects around usability, ergonomics, color implications and other significant but often overlooked human aspects to UIs.
Test and Fix: Here, as with any normal IT project, the completed solution is put through its paces to ensure that all component elements and the integration are working as expected. This is completed by a combined team of IT experts and real business users. -
Training and Roll-out: Again a typical phase of any IT project where testing has completed and all issues have been resolved. The benefit of the ZUI approach however, is that due to the intensive requirement gathering and blueprinting work, we have found that testing and roll-out will result in:
- Dramatically reduced defects
- Extensive reductions in training needs
