Good but not best solution
In out-sourcing software industry, one of the most important things the offshore development must focus that is project's scope. All things are defined in project's scope are the commitment between us and customer. Project's scope also be the main value to calculate the cost of project. Whatever artifact you do outside the project's scope is free and it is not charged to client. However, to strengthen the relationship between us and customer, offshore development would implement additional things that are not defined in project's scope. Do for free can attract the client also that causes client will ignore some our mistake while development due to the good relationship between sides. But offshore development team should be careful on defining solution that is not belong project's scope.
Say in other words, project's scope is what client needs in their product and it is a must for them in almost cases. It is great if you provide the product on time with high quality that fulfill all requirements defined in project's scope and plus some additional features outside project's scope (that is treated as a gift to client). However, when development team can not do that, they must implement things are defined in project's scope first with no objective. In practice, when choosing solution, almost team would like to choose the best solution to solve problem; many cases, the best solution can cause the conflict with timeline, resources and provider to client over what they needs. Development team tend to think client will be aware with their effort, their dedication also the solution is better for client's business. But we can not be sure whether this solution is better for customer's business without asking them (if you think it is better, please providing your suggestion, if client agrees the project's scope will be changed and schedule/resource can be changed also) and implement without any concern about timeline and quality. "The more you do, the more mistake cause by yours", team do much but client does not appreciate what they do while team expect the client satisfy their performance!
So while you choose any solution, team should consider the timeline and especially project's scope. Whenever, you complete the project's scope within timeline, it is time for you to consider provide gifts to client by improving the quality but you should limit adding additional features if needed. Not think that client will be aware your performance while you provide them the product is different project's scope, it has more functionalities but more defects also it is delivered late than schedule.
Thanks for the blog post. I think that, if a company has made the decision to outsource its data processes, they need to iron out every last detail. These include explaining exactly what needs to be done, the results that they are expecting and the timetable when they expect to see said results. This way, no detail seems vague and mistakes are minimized.