Dashinginfo is experienced in different engagement models. And we would suggest adapting suitable engagement models based on the client.

1. Categorized by project governance model

a) Professional model

The individual technical engineers from Dashinginfo become an expansion to the client project team, and are supervised by client project managers or leads. When in this model, our client takes full responsibilities of project management.

Why choose this one?

• When our client runs out of sufficient resources in a project, or short of certain specialties
• When our client needs to have Dashinginfo engineers to work onsite specifically
• When our client needs to work with Dashinginfo engineers closely enough
• When our client needs to take over the control of delivery quality from Dashinginfo
• When our client needs expansion but cannot prove for internal headcounts

b) Co-Managed model

Co-Managed model is somewhere between professional model and managed model. When running with this model, our client is still responsible for the project key processes or checkpoints, and Dashinginfo only takes responsibilities within the scope of certain specific tasks. In this way, our client controls key factors but can get rid of the management overhead on all detailed micro-managements. Our clients usually are only responsible for choosing Dashinginfo engineers on key positions, define delivery scope, define project processes, and communicate with the Dashinginfo engineers on key positions. Meanwhile, Dashinginfo will have a person in charge of our own team members, managing the daily detailed activities and report to the project owner from our client.
This model allows Dashinginfo to understand the expectations of the project owners (clients), and leads the engagement to a further stage – project base model.

Why choose this one?

• When the software product or application is so essential to our client that it cannot be fully taken over by Dashinginfo
• When Dashinginfo has understanding on the client industry knowledge and project processes
• When our client does not feel quite confident to have Dashinginfo taking full control

c) Managed model (fully outsourced)

Managed model is an end to end delivery model, and is considered the best for long term engagements. When working with this model, our client focuses on their core business, while Dashinginfo is responsible for the project delivery and setting expectations of the client project owner. With this model, Dashinginfo can manage the project more independently, making it possible to become a long term strategic partnership. And based on our past experiences, the results will ultimately benefit our clients. With this model, Dashinginfo can leverage our own best practices and methodologies into the project delivery.

Why choose this one?

• When the scope and deliveries of the project can be clearly defined
• When Dashinginfo has a deep understanding of client requirements, and our client is confident to transfer this job to us.
• When the working location does not have to be limited in “onsite”

2. Categorized by project pricing model

a) T&M (Time & Material)

T&M is a model where the servicing fee is calculated on actual amount of work that took place. Based on the rate, usually hourly rate, negotiated between Dashinginfo and our clients, Time Sheets are used to record the actual amount of work in hours. This model is usually adopted when the project scope cannot be pre-determined, or the deliveries cannot be clearly described, or for most research programs.

Why choose this one?

• When there are too many unknown issues that may affect the scope or delivery of the project
• When our client foresees a significant amount of increase or decrease in the team size
• Initial stage of a new project, or a research program

b) Fix price model

Fix price means the project total amount of cost, project deliveries, and delivery milestones are defined and described before the project started. With this model, our clients can have an accurate figure of budget needed, and when the estimation is relevantly accurate, can have the best return of investment. On the other hand, Dashinginfo can also make investment on the project, which can also increase the return to our clients.

Why choose this one?

• When the scope and deliveries are clearly defined and described
• When requirements are clear at the beginning of the project
• When both our clients and us can follow the standards of IT processes
• When our clients and us can run a routine review
• When the service fee can be divided by milestones

Engagement model in practice Usually, when a project is outsourced to Dashinginfo, the execution is a combination of both project governance model and pricing model. Based on different business or industry, the combination could be various. For example, in a software product engineering outsourcing project, it is common to see an outsourcing project for only one or few components of the product. At the initial stages, our client project owner takes full responsibilities of the team management and builds up the team, which means it is a professional model plus T&M. Then after the team has 1~2 successful deliveries, there will form a project lead from Dashinginfo, taking charge of the Dashinginfo engineers. And the client project owner will work with our project lead, having our project lead take over the micro managements. So now it becomes a co-managed model plus T&M. The next thing that will happen is when the delivery team of Dashinginfo grows mature and the next deliveries can be clearly defined, our client agrees to have us take over the entire project. So this is becoming an end to end delivery, which is an offsite managed project plus fix price.