We are a software development company with more than a decade of experience. We believe that the solution to outsourcing is to establish proper communication, thus ensuring quality and on-time delivery of customer expectations.

Menu

Category Archives: Communication

We have a very skillful and experienced team, while the customer has a problem, solving which would improve their business.

In order to provide a high quality and timely solution to the customer’s problem, we need to ensure good communication between the customer’s experts and our team. To achieve this we concentrate on understanding the customer issue, describing the proposed solution and communicating our plans and progress to the customer, before the development starts and at any stage in the development process.

In this section you can find out the different methods and processes that we use in order to ensure that no georgraphical, language or cultural barrier stands in the way of achieving a success in our customer’s projects.

Before you build a complex system — it is best to ensure the task is understood well. It is better than having to redo it later. For this we use a number of techniques, from early prototyping to detailed specifications with screen designs and algorithm descriptions.

There are many organizational difficulties facing small to medium Software Quality Assurance (QA) teams. Because of this, we welcome any help to simplify this work and make assignment, communication and reporting more reliable. Tools are not the silver bullet, yet with a responsible team the right tools can make a lot of difference. Read on to see how we started using Google’s toolkit (namely, Google Wave and Google Docs) in our daily QA and general development practices, as described by Dmitriy Boltovskiy, our QA team lead.

Last December, we decided to redesign our website, and, due to lack of resources, wanted to hire and external shop to do it for us. After the requirement discussions and resulting budget calculation, we decided to design and implement our website ourselves. Yet some lessons were learned, which I would like to share below.