Introduction

Many projects are initiated too fast, only focusing at some parts of its feasibility, and fail. An assumed (or real) pressure, generated due to time and budget reasons, forces to a fast and unprepared project kick off. This is the start of failure.

Our projects are not only technically prepared and executed but also with necessary methodologies and business know how.

This guarantees a successful, efficient and professional project realization.

Analysis and Specification

Basis of a project kick off is a clear overall understanding about project methodologies, its set up and execution where the customer is tightly involved. This makes the project transparent and controllable through every step.

The project methodology consists mainly of the following steps:

• A feasibility study: Based on the main processes, use cases and the overall technical architecture.
  Result: an initial project plan as basis for required resources and project deliverables. Only when the customer has approved the project plan the next step can be tackled.
• A specification phase: Based on the Use Cases the functional, non-functional and technical specifications are detailed. The test scenarios and test cases are defined in parallel.
  Result: the test documents will be the basis for the final acceptance test of the solution. This phase requires a tight and active involvement of the customer.

Has the customer approve this phase the development of the solution can be triggered.

Development and Approval of the Solution

This phase starts with a pilot. Here it the customer gets a hands-on of the user interfaces (as detailed as possible) and allows simultaneously to do first (“desktop”) tests of the key functionalities. After the validation of the pilot by the customer the project plan will be fixed and the development starts.

Project Management, Transport and Logistics