<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:s="http://www.techrepublic.com/search" xmlns:dc="http://purl.org/dc/elements/1.1/"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title><![CDATA[Discussion on How to successfully work with an offshore team ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-279187]]></link>
    <atom:link rel="hub" type="application/rss+xml" href="http://pubsubhubbub.appspot.com/" />
    <atom:link rel="self" type="application/rss+xml" href="http://www.techrepublic.com/forum/discussions/102-279187/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-05-20T07:04:17-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[Process]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-279187-3417587]]></link>
        <description><![CDATA[Instructive video. I think it touches on some of the 'points of attention', things people need to learn in order to understand eachother from both 'sides'. I believe that setting up a documented process before you start working with your indian team is the best starting point. This makes everyone involved think 'how' they are going to work before 'getting things done'. I have written some other usefull tips on this blog: http://www.bridge-outsourcing.com]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-279187-3417587]]></guid>
        <dc:creator><![CDATA[hugomesser]]></dc:creator>
        <pubDate>Wed, 09 Feb 2011 23:10:06 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[RE: How to successfully work with an offshore team]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-279187-2663341]]></link>
        <description><![CDATA[I am at offshore-India. I recently work with onsite team, the project went into trouble times, easy, I got fired :)! The good part of this assignment Offshore team, we, upfront honest with the skill levels to save embarassment in future.More communication planned and we were proactive in bringing issues very early, but I dont know, what onsite team have their Project Managers mind, they were delaying responses for issues, but when task got delayed, trying to show up that highlighted in meetings... We did not raise voice upfront, as we were waiting time to reap to realize themselves about the gap. I see mistake from Onsite as not providing clarity and details, and Offshore team not bringing this issue upfront in meetings to wake their top management, later it got blamed for poor deliveries. Bottom line, Communication &amp; clarity both sides is paramout to project success. In this world, Onsite team or Offshore team, its the individuals who are open and honest in interactions in business will get up this world to speed, rest will fade soon.!-Honest Indian]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-279187-2663341]]></guid>
        <dc:creator><![CDATA[kphani_prasad@...]]></dc:creator>
        <pubDate>Thu, 18 Dec 2008 00:37:17 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[In defence of an onsite resource]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-279187-2643418]]></link>
        <description><![CDATA[In my current role, I am what Jason would describe as an onsite resource or the more appropriate marketing term would be - &quot;Customer facing end of the global delivery model&quot;.  Though, I agree with the most of the points that Jason brought up during the video presentation. In my mode of operations I fill in lot many shoes. Not only I am part project manager, I am part time system architect, business analyst, technical team, programmer and English-2-English translator. I believe having a onsite liason is vital for success of any outsourced project, especially if you are trying it out for the first time. Yes, there is a cost associated with it but in most cases, it is less than what the market would demand for a US based senior programmer. (Mind the word, most cases).In the examples for programming, I believe it is also IMPORTANT set up the proper infrastruture - like access to common code repositories and build/source control processes, such was what files can be checked out by multiple people and some which cannot be shared (or are risky to be shared) such as Visual C++ resource file, should be checked in by Eastern Time so and so, and for resource in US, before their end of the day.Overall a good show.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-279187-2643418]]></guid>
        <dc:creator><![CDATA[CodingUnknowingly]]></dc:creator>
        <pubDate>Thu, 20 Nov 2008 03:38:48 -0800</pubDate>
    </item>
    </channel>
</rss>

