APPROACH NARMA 42

Start with a pilot or prototype to discover and understand the problem. The real problem might be different from the problem as perceived by the client.

Set up a complete (scientific) model of the problem. This is the analytical / abstract phase. In this phase also the description of technical solution, including infrastructure requirements (WL licensing, servers, public/private cloud, etc.) is outlined. This phase leads to a proof of concept.

Developing and implementing modules according to a pre-defined timeline.

In every phase lurks the risk of failures. This is an unavoidable trait of problem solving.

Our working attitude is: Fail Fast. The sooner we find that an approach does not work, the better. This is in everybody’s interest.
In each phase we assign group members who are best fit for the job at hand.

Each phase can be contracted separately by the client.

In the Exploratory phase there is a shared risk for client and us: therefore this is offered for a fixed amount of time and a fixed price.