Onshore work methods V Offshore Supplier work methods - how to strike a balance?

Question

Any advice on the best way to strike a balance between the work methods of an offshore supplier and the work methods of a new onshore team?

We have an offshore supplier with about 2 years who have their own working practices and methods. I was bought in as the first onshore developer for my company with the view to vetting the code that comes in and putting together some best practices.

Now from what I've seen there are lots of holes in their process (e.g. estimation, planning, code reviews, coding standards from about 10 years ago, no concept of mocking, refactoring etc).

I need to be seen as a problem solver and not a problem creator but also I need to try and be somewhat forceful of what they are doing needs improving and at the end of the day they are a supplier. I would appreciate any advice.

Thanks.

Answer 1

I can see that you have an uphill task up your way.

First thing you need to understand is that you cant change the system in a day. I was you, I would have followed steps as below.

1. Form a Road Map of all the thing you would to change/introduce.
2. Rely on your strong negotiation skills rather using terms like FORCEFUL(CONTROLLING IS BAD!)
3. Get a tentative consensus for all members on implementation and that depends on power of communication or negotiation. If you think, you are not good that, Take help of a senior member of team.
4. Prioritize the changes (classic change management) and form implementation strategy. Start kicking on. Invoke the interest of entire team as if something great is going to happen.
5. Work very hard! Changes can only be manager when great teams are behind you.

Hope that help!