Engagement models.
What each way of buying software capacity commits you to, from staff augmentation to a managed offshore team, and which suits a growing roadmap.
Choosing how to buy software capacity.
Every engagement model commits you to something different. These eleven guides set out exactly what, so you can compare staff augmentation, outstaffing, outsourcing, an offshore development center and a managed offshore team on equal terms before a provider frames the choice for you.
The models differ on one axis more than any other: who is accountable when the work is late. Under staff augmentation the answer is you, because you are buying access to a person's time and directing it yourself. Under a managed service the answer is the provider, because you are buying delivery of the work. Rate cards, contract length and location all follow from that one answer.
The second axis is cost, and it is rarely the number on the quote. When you run the people yourself, management time comes on top of the rate. Our own estimate, from engagements where the client runs the people, is four to eight hours a week per specialist. Turnover adds weeks of ramp-up every time someone leaves, which is why the average tenure of a provider's engineers belongs on every comparison.
That is also why the same arrangement carries several names. Offshore staffing, outstaffing and body leasing describe broadly one commercial model in different markets, and an offshore development center can be run either way, depending on who supplies the management. The software development outsourcing guide is the best starting point if you are new to the subject.
If you already know you want the provider to be accountable for delivery, how it works shows how a dedicated team is run day to day, from the first call to a team in your sprints four to six weeks after signing.