Software development

Experience gained from many projects we created let us develop our own methodology of generating software. It was created on a basis of Agile/extreme programming and its main goal and asset is to turn to the client and his needs together with delivering most valuable products.

We value:

Individuals and interactionsover processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
from Agile manifesto

Although the elements enumerated on the right are crucial in the process of the creation of software, they are rather of an operative kind. Concepts enumerated on the left are more strategic, that is why we focus on them in processes of software engineering.

Why Agile?

The traditional method of a software production constituted by four subsequent stages without the ability to return creates many problems and it often contributes to the raise of expenses or even the failure of projects. It happens because:

it's impossible to gain all demands in the initial phase of a project
needs change during the process and only then become fully understood
correction of misunderstandings emerged in initial phases of creating is very expensive
external conditionings, not considered in a planning phase, change
application of new technologies and tools causes that a project becomes unpredictable, which makes goals impossible to achieve

Agile software

A response to those scarcities are nimble and light methodologies of generating software. The idea is to divide the project into small problems and to solve each one of them in a short period of time. The basic unit of time in this methodology is an iteration which lasts approximately two to four weeks and is constituted by the following phases:

consultation with a client
creating the script of a user
defining tests
implementation
refactorization
demonstration of a solution

It is very important that every iteration is realized in close cooperation with a client which allows us for current modification of aims and demands of a project, correction of mistakes emerging as a result of misunderstandings and controlling the whole process. Adaptive management of software is based on various rules and norms such as:

Quick win

One of the advantages of our approach to the production of software is continuous delivery (after every iteration) of new versions of a product to the client. It helps to confront intentions and expectations of a client (which often evolve) with a factual product and to modify it even during late stages of creation. Agile allows for quick execution of such changes and reduces expenses to a minimum. In the case of disruption of the project for various reasons our client remains with a working system of functionality on the scale of invested resources. Quick win is also an excellent measure of work progress.