Communication with a Customer :-
The customer resolves all issues by communicating with the assigned Project Manager, responsible for planning the work, performing overall management and tracking the progress. Customer side. It is reasonable that the customer assigns a responsible contact person, e.g. a Project Coordinator, to address all possible issues from SSS team. Communication is carried out by email, instant messengers, phone and personal meetings.

Planning and Reporting :-
A detailed plan is created at the beginning of each phase and updated by the project manager at least weekly. This allows transparent tracking of the status of the project and provides a clear vision of the cost of the whole project and its every step.

Requirements Management :-
From the experience we know that creation of a visual prototype of the future solution (just a GUI, look and feel, real controls and navigation) at the requirements gathering stage is an effective practice. Its purpose is to let the customer “feel” the future solution and probably adjust the requirements at the very beginning.

Change Management :-
All requests are sent to the change requests pool accessible to both the customer and SSS manazgers. The pool serves as a base for future iterations scope planning. This approach allows the customer to easily control timeline and budget of the project.

Risk Management :-
There are some risks for offshore projects and many offshore teams tend to ignore them, which leads to failure of software development projects. Our experience of efficient risk management allows us to avoid them and finish the project in time and within budget.

Competence Transfer :-
Competence Transfer involves documentation and knowledge transfer including transfer of specifications, design, test, release, guideline documents and user manuals and end user or administrator trainings.