Agile assignment in Bangalore

As some of you will already know, I’ve just finished a three month engagement for a Wall St bank, helping them refine their use of agile development practices. I’m going to refrain from comment on the specifics of the engagement, and instead focus on the things that I learned myself.

1) Indian programmers are just the same as western programmers – same strengths, same weaknesses. Some are good, some are not so good, some are quiet, some are extroverted. I’ve know this intellectually, but now I know it emotionally as well.

2) Recruitment in Bangalore is just as difficult as it is anywhere else. It might even be harder, since in Bangalore you’re competing directly against Microsoft and IBM (who were on the same campus I was on), as well as Google. Most of us don’t face that level of competition in our local regions. And sure there are lots more graduates in India, but if you want people with 5 or 10 years experience the ratios are less favourable. Plus Infosys wants thirty thousand new programmers in 2007 (anecdotally), and that might include just a few of the good ones ;-)

3) There are cultural differences, but they are swamped by the twin tyrannies of distance and time zones. Remote offices are dealing with comparative strangers, and between the USA and India there are only a few hours of effective overlap in a day (it’s a bit better between India and Australia). Communication over email and phone just isn’t the same – you need lots of face to face experience to overcome this.

4) For distributed development you need people who are willing and able to travel. Include that in your profiles.

5) You can’t effect rapid change in a distributed group, especially if there isn’t a strong consensus to begin with. And forming that consensus takes a long time. The Forming-Storming-Norming-Performing cycle takes a lot longer for a distributed team – there are plenty of opportunities for miscommunication, and it takes a lot longer to sort the miscommunications out.

6) Everyone’s ability to influence is diminished by distance. This was certainly a personal challenge, and I don’t feel that I really rose to the occassion.

That’s enough to get the things that are distracting me out of my head so that I can focus on some pressing work, but I’m sure that more things will occur to me later. When I get a chance to right a blog while I’m online I’ll include some photos so people can get a better sense of the work environment here in Bangalore.

~ by Steve Hayes on November 21, 2006.

2 Responses to “Agile assignment in Bangalore”

  1. Ah, finally the post I was waiting for :)

    How are companies dealing with this competition from Microsoft et al.?

    I hope the family are coping ok with my bustling hometown. Did you get to walk across the Golf course?

    Looking forward to reading more of your reflections on your experiences in Bangalore.

  2. I’m sure that some companies are accustomed to competing with Microsoft for talent, but it’s definitely a challenge for a Wall St bank! When you’re in New York you’re dealing with people generally have a financial background, they have some idea of who you are, and their application probably means they have some expectations for what the work will entail. The candidates are probably domain oriented.
    Here I think candidates are technology oriented, not domain oriented, and the name of the bank doesn’t really hold any kudos for them. But at least it’s a big Wall St bank, and you could look them up on the web and possibly be impressed (if you have some knowledge of finance). It must be brutal for Australian companies, with generally lower profiles, to recruit here and I suspect that most candidates will use those posts as stepping stones to something else.
    Family are holding up fine, and have adapted much better than I have – they get to deal with India seven days a week, while I spent five days a week cocooned within the bank.

Leave a Reply