I have a competitor of yours trying to get a meeting with me. Their pitch is that I can have 10 programmers at $20/hr each, a 75% savings based on US programmers!
The problem is I want solutions, not man-hours!
11–20 of 97 posts
I have a competitor of yours trying to get a meeting with me. Their pitch is that I can have 10 programmers at $20/hr each, a 75% savings based on US programmers!
The problem is I want solutions, not man-hours!
India is a big place. To me that is like saying, "what are your views on development agencies based in the world?"
I see this question asking about what it's like working with India-based dev agencies, taking into consideration cultural differences.
It would be just as valid if asked about other parts of the world.
I have experienced working with two different Indian development teams and both of my experiences were characterized the same: 1) Over-communication to a fault 2) Low code quality I don't know how can you change my perspective, but I would suggest not trying to change the perspective of Indian agencies as a whole - but rather why you are different than the stereotypical Indian agency.
Perhaps the key thing is a tighter attitude to specialisation: most Indian (and, for that matter, far east Asian) development teams tend to have a "we can do everything across a billion platforms and techs" approach, where it might be better off concentrating your offering down to a few key techs, and really doubling down on the quality of those.
So, you can certainly try to put lipstick on your pig, but we all have 20 years experience with that pig And we know that it's a pig, even if you dress it up.
Other experience, estimates are wrong, filling in more hours than actually worked and they always say yes. But what they mean is we can't or don't understand what your mean and we will stall the project.
I have experienced working with two different Indian development teams and both of my experiences were characterized the same: 1) Over-communication to a fault 2) Low code quality I don't know how can you change my perspective, but I would suggest not trying to change the perspective of Indian agencies as a whole - but rather why you are different than the stereotypical Indian agency.
What do you mean by over communication? Do you mean that essential communication is repeated without additional effect? Or that unnecessary details are relayed?
I have experienced working with two different Indian development teams and both of my experiences were characterized the same: 1) Over-communication to a fault 2) Low code quality I don't know how can you change my perspective, but I would suggest not trying to change the perspective of Indian agencies as a whole - but rather why you are different than the stereotypical Indian agency.
What do you mean by over communication? Do you mean that essential communication is repeated without additional effect? Or that unnecessary details are relayed?
I have experienced working with two different Indian development teams and both of my experiences were characterized the same: 1) Over-communication to a fault 2) Low code quality I don't know how can you change my perspective, but I would suggest not trying to change the perspective of Indian agencies as a whole - but rather why you are different than the stereotypical Indian agency.
1) To address the over-communication we have stopped working on fixed price projects, and rather worked with customers as their extended team
2) We as a group of individuals are trying hard to change this perspective. Our Computer Science education needs to be blamed as well
3)I have created a very interesting slide on our deck https://goo.gl/5jvN6R
Cheers