Development Processes: Hindrance or Help?

We think that the right dose of processes releases time for a creative solution of the technical tasks you pose us. This because sensible processes and tools are simplifying repetitive jobs, but first of all because they map existing experience and make it easily accessible.

Our processes are always about the usage of templates or tools: it must be easier to follow the process than to reinvent the wheel. If you have to write e.g. a specification, it is easier to work with a template containing already the structure and part of the content than with a white piece of paper. In addition the chances are lower that important aspects get lost.

In order to allow us to execute projects from consulting over rapid prototypes as far as safety related systems, all processes can be tailored to the project at hand. This goes from completely "switching off" a process to multiple reviews and audits of its results.

Our project life cycle is derived from the V-model. It can be adapted through a loose or strict sequence of the input and output gates of the phases, in addition the number of iterations (functional prototype, first prototype, second prototype... or agile software releases) can be adjusted. This means that we can tune quality and effort optimally for your project.

We make a point of keeping our processes workable and efficient. This is e.g. why they are stored in a Wiki which allows easy access and simple changes. In our research and development they are continuously improved. This results in productive and low-risk projects for you, e.g. our effort estimations are on average more accurate than 20%.

Show me how this works!