Working with a system integrator

Three parties sit around a cloud ERP project: the customer, the software vendor, and the implementation partner. Who is responsible when something breaks has a different answer depending on which of the three you ask, which is exactly why it is worth a lesson. A typical team shape: a programme manager, functional leads per tower, a technical lead, a data lead, and change and training. Most people taking this course are either the functional consultant or the client-side counterpart, and the same project looks quite different from those two chairs. What goes wrong commercially, in roughly the order it bites: Scope defined by module rather than by business process, so the gaps between modules belong to nobody. Design decisions made by whoever happened to be in the room. No decision log, so the same argument is had three times. Testing scoped as an afterthought, then compressed when the build runs…

In this module: Module 1 · The Financials Landscape

1. 1The application family
2. 2The data flow mapFree preview
3. 3Navigating the application
4. 4The Setup and Maintenance area
5. 5Rapid vs. full implementation
6. 6Working with a system integratorFree preview
7. 7Lab: navigate the setup area