In practice, this phase-oriented approach has proven:

1. Kickoff: with adoption goals, project plan, schedules and responsibilities
2. Test system: Installation of the test system in the standard
3. Specification: creation and adoption, if necessary, with state analysis / target sequence organization
4. Interface specification: implementation and testing of interfaces on the test system
5. Implementation of the specifications on the test system
6. Training of key users remotely or on-site
7. User training by the key users ("Train-the-Trainer")
8. Test / parallel operation
9. Declaration of readiness decrease based on the requirements specification
10. Real start preparation like moving on the live system
    
11. Golive / Real Start
12. Project completion and documentation
13. Optimization

After placing the order S4P defines a project manager and account manager. He or she is the customers contact person during the entire time. On the customer side, a project manager and the project should at least be named at the kickoff. S4P takes on the project overall coordination. Our "Who does-is-what-to-point" list has been proven. All projects are monitored by Prof. Dr.-Ing. J. Berlak. All points of the specifications are maintained in our web-based JIRA system.

A central part of the introduction is the establishment and acceptance of the specifications by the customer. The specification serves as guideline for the implementation and is based on the acceptance by the customer. At the same time the specification is also used to project documentation.

S4P recommends using a separate test and live system preferably in the form of two virtual VMs. There are basically no additional license cost for a test ystem! Updates should always be recorded on the test system and released before rolling out.

Benefits:

• transparency ↑
• responsibilities ↑
• knowledge management ↑
• leadership development ↑
• risks ↓
• effort ↓
• reactive power ↓
• "Great, another makes it" ↓