site quest
inspired software engineering
Main Software Development Engagement models

Engagement models

Our Engagement Models accommodate all features, necessary for successful collaboration

Project based (fixed price)

By the Project Based approach we mean outsourcing of a specific software development task, whether it is a new solution development project, re-engineering or migration task, solution improvement or customization. The main distinctive feature of this type of engagement model is that the contract has all of the specifics of the project; like uniqueness or predefined time frame or fixed budget. This approach usually implies a fixed cost for the project and the risks are mostly on Softengi.

Dedicated team

Dedicated teams and developments centers can be very efficient in certain conditions. There are different cases where this type of model is ideal. The main differentiation of this approach is that the team usually follows client's practices, methodologies and culture. They become an extension of your internal team (just like having some of your staff in another building). The customer can be sure that all activities inside the dedicated team are similar to ones he has on-site. The service provider is mostly focused on the processes of team building, team monitoring, managing customers and employee's expectations, managing the personnel related risks. And in most cases the customer (along with the assigned Softengi project manager) is managing the projects performed by the team using its own management staff.

Time & Material 

This model is usually used when our clients have a need to temporary extend their team with additional consultants or engineers. The reason could be to either increase productivity of their team or to involve specialists with specific skills to perform a particular task. This model can also be used as the first step of a feasibility study of the dedicated team model for the customer at the offshore location. Another example is when a client might have a constant flow of tasks which they are not able to plan in advance. This might be seen in the third-level support of one of their systems where tasks are arise from time to time and it is not reasonable to keep the team permanently. 


SLA Approach 

The SLA (Service Level Agreement) model is typically used for support and maintenance of systems. The SLA provides services with clearly and strictly agreed constraints and requirements.

When we talk about a SLA for IT services it usually includes the following activities:

- Incident Management (supports the restoration of normal operational services as quickly as possible and minimizes the negative impact on business operations)

- Problem Management (comprehensively records incidents in order to identify the cause of the incidents and trends)

- Change Management (controls changes to the services)

- Release Management (ensures that only authorized versions of software are made available for operation)

- Service Level Management (ensures the quality of the IT services provided)


 Contact us to discuss which model or their combination fits best your needs.