FAQ

Question: How is your working process organized?

Answer: The working process looks like this: together with the customer we write a software requirements specification and define the dead-line. The key characteristic of our work is that we divide the whole work over the project into several substeps. Ideally, 3-4 weeks each. Within every substep we complete a certain amount of work which, after it has been through the full QA cycle, is implemented at the customer’s location.

Question: Why is this approach good for the customer? How does it help to minimize the customer’s risks?

Answer: This approach gives a lot of advantages to the customer. Firstly, it means continuous control over the work being done. And not just at the level of "reports" but in the shape of a continuously working system. Secondly, the customer has at his disposal a ready program from its early stages of development (i.e. for a project with one-year time limit — already in a month — in the form of a version with the basic functional). Thirdly, the customer runs minimal risks as he pays only for each completed substep.

Question: The substeps are finished and the program is implemented. But the requirements specification was written long ago. There have arisen many new requirements since then. What can you do about that?

Answer: We prefer long-term relationships. After the main work over the project is done we provide technical support and add the required functional.