Re: Re: What are the most important issues during offshore software development

Thanks for your share. Good points, I think.

Regarding pointing out the mistakes, maybe it is complex sometimes. You know
nobody hope to be found wrong.

But such mistakes must be pointed out if existed.

So the TDD is must. Let testing find out all possible mistakes and achieve
monitor.

On Thu, Jul 3, 2008 at 11:03 AM, Kalpesh <shahkalpesh-/[email protected]> wrote:

>   Hi Forrest,
>
> I have worked on a few project (from the other side)
> i.e. I have worked for a company in India who received offshore work
> from US & other countries.
>
> In my experience, these things are important
> 1) Constant feedback.
> 2) Everyone understands what needs to be done & project goal in detail.
> 3) Team should be able to point out mistakes & clarify things
> proactively. I mean - requirements ask for 2 checkboxes in GUI where a
> 2 radio button is good solution. So, the team should be open to point
> out flaws than doing it all wrong rather than let mistakes be
> corrected by client & then re-work.
> 4) Regular monitoring (although, no micro-management)
> 5) Setting the expectations
> 6) Rotating (client comes offshore OR people go onsite from time to time)
> 7) Ask the team to be open to say "no" (in India, its not good to say no)
>
> More than anything else, trust is the key (no fooling around by either
> side) and working as a team (rather than offshore team and onsite team)
>
> HTH
> Kalpesh
>
>  
>



-- 
Everything is under the questions of What , Why and How !