Work Methodology

Dedicated to our clients

We prefer to invest a significant proportion of time early on in a project to get to know our client better. We believe our chance of satisfying our customer will be higher when we fully understand the client's business before we start designing what we will develop for them.

Understanding the clients’ business needs

Our experience shows that a request we get from a client seldom guarantees him getting the solution for his real problem. Knowing that, we first focus on the problem definition by talking a lot with the client. Our aim is to "feel" what the client feels so that we can give the best possible advice and create the best possible solution. A long-term solution.

Emphasis on clearly specifying client needs

We begin every software development project with a very high standard of functional and technical specification. We design so called ‘use cases’ in close cooperation with our clients in order to show the workflow in use and then translate those use cases into a functional specification for a higher level of confidence in accuracy. Once the specification is approved the development team can get to work - and we will frequently ask the client for input during development in order to guarantee we completely deliver on their wishes.

We use Agile methodology (http://agilemanifesto.org/)

In the area of project management we have adopted Agile methodology and we rely on SCRUM in the software delivery. This new approach requires the client to be involved in the whole project development cycle from the very outset. As a result, it minimizes the risk of exceeding the budget and not meeting the deadlines. The client is more in control and can easily influence the end result. Agile method increases the chances of the solution meeting clients’ expectations since any potential issues related to the project are detected at the very early stage.

In the majority of our projects we follow this approach:

1. Project intake – we define the core functionality and the scope of the project.
2. Project kickoff –we analyze the most important features and prioritize them together with the client. The tasks are broken down and arranged into sprints.
3. Project implementation –daily SCRUM meetings measure the progress and detect the issues that are blocking the team. Clients receive progress status reports on a regular basis. At the end of the sprint we deploy the solution for client’s review and approval.
4. Project deployment –we usually present the result of our work to the customer at the end of each sprint.