Integration projects can often be complex, especially when many systems are supposed to be integrated with each other. We therefore recommend an app-by-app approach. Here, the complex overall project is divided into subprojects. Usually, a subproject is the integration of two systems. Often, however, a subproject can only include the integration of two endpoints of two systems. This depends on the project circumstances. When the project is completed, i.e. the data is successfully synchronized, the next project is started.
We assist you with projects and support from planning to operation via Professional Services.
At Marini Systems we always implement (sub)projects according to the same scheme. We outline the scheme for you here:
The basics are:
- Project owners are informed at all process steps.
- All documents are stored in the appropriate project directory.
- A project is always followed by another project.
The individual steps run as follows:
Basic Setup
- All systems, applications and configurations required to implement the specifications are set up completely and independently by the customer.
- The setup must be accepted and released internally.
- After setup and release, the customer is informed.
Individual Development
- All individual specifications are set up completely and independently by the customer.
- The setup must be accepted and released internally.
- Extensions and adjustments to the specifications are documented (Specification Extension).
- After setup and release, the customer is informed.
Tests and Adjustments
- The state of affairs is checked in a detailed exchange with the customer and adjusted if necessary.
- The result must be accepted and released by the customer.
- Extensions and adjustments to the specifications are documented (Specification Extension).
- Extensions, adaptations and ideas that have not been taken into account are recorded in the backlog
(planning of future projects). - After completion of the work, the customer is informed.
Delivery and Training
- The result is documented for the users and the documentation is made available to the users.
- Users are trained and the result is taken into productive operation.
- Extensions, adjustments and ideas that have not been taken into account are recorded in the backlog
(planning of later projects).
KPI and Reporting
- The result is used by the customer and should fulfill specified requirements there. The development and success of the result should be visible to the customer. Success indicators should be defined and made available to the customer (example: BI dashboard, reports).
- All results from the project are summarized and made available to the customer for completion.
- The customer will be informed about the project completion.