Hi Mike,

We've had  a permanent onshore/offshore product team for just over 2 years
now, with a similar approach to what you're suggesting:

       * Strategy, architecture and UX onshore
       * Coding in China & Bulgaria
       * Quality/Review back onshore

It’s working really well now, once we fully appreciated that an offshore
needs to be managed the same as an onshore team (seems like a stupid
oversight, in hindsight)

       * The offshore team has to be properly managed every day.  At first
we would assign a discrete project and expect it to come back magically
completed to expectation a week later.  Sooooo naïve.

       *  Make sure your onshore team has experience managing people and
that they actually want to manage people.  I made the mistake of assuming my
lead onshore developer wanted to move into a management role.  It wasn’t the
case and resulted in a bumps.

       *  When you’re testing or trialling an offshore team, pay real close
attention to the questions they ask.  You want to see if they quickly and
fully comprehend the project (both from a technical and user perspective) as
well as the quality of questions asked.  We actually tell them at the start
of a trial how important the questions they ask are.

       *  Initiative.  You want to make sure your offshore guys will raise
issues with you and seek out their own solutions. We found that with some
candidates there seemed to be a cultural issue at play.  Everything was
always “ok ok” … until it wasn’t.

The other little requirement we have of onshore/offshore teams is that at
the end of every day they answer 4 simple questions and send that to the
group:

    1. What did I work on today?
    2. What were the challenges I encountered?
    3. How I overcame those challenges
    4. What I am working on tomorrow

You can read more about how we rolled this out here:
http://www.worketc.com/blog/Development/105 

Hope that helps and good luck!

Daniel Barnett 
CEO - WORKetc
-----------------------------------
E: [email protected] 
W: www.WORKetc.com



-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of mike@mrKruntz
Sent: Sunday, 1 July 2012 7:54 AM
To: [email protected]
Subject: [SiliconBeach] Blended-shore dev teams?

Hey all,

I was hoping someone here may be able to help me out? I've noticed a rise
recently in dev teams taking a blended shore approach to their business,
having architecture and strategy managed locally and coding and manual work
done overseas (china, Philippines, Ukraine and India predominantly).

I know most people here would probably be in favour of internal and local
teams but for rapid prototyping, this approach may be advantageous and cost
effective.

Does anyone here have an insight or experience working with a blended-shore
company (good or bad)?

Disclaimer (I'm currently searching for a project based dev team to rapid
prototype a number of start-up concepts)

Thanks heaps !

-- 
You received this message because you are subscribed to the Silicon Beach
Australia mailing list. Vist http://siliconbeachaustralia.org for more

Forum rules
1) No lurkers! It is expected that you introduce yourself.
2) No jobs postings. You can use http://siliconbeachaustralia.org/jobs


To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/silicon-beach-australia?hl=en?hl=en

-- 
You received this message because you are subscribed to the Silicon Beach 
Australia mailing list. Vist http://siliconbeachaustralia.org for more

Forum rules
1) No lurkers! It is expected that you introduce yourself.
2) No jobs postings. You can use http://siliconbeachaustralia.org/jobs


To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/silicon-beach-australia?hl=en?hl=en

Reply via email to