Skip to content

distributed agile

Onsite Business Analyst

This has come up in various discussions recently and I want to put down my thoughts about the role and responsibilities. For a ThoughtWorks team in India (or China) most of the work is offshore agile development. Clients are usually in the UK or the USA. The team is structured as follows: Offshore PM Offshore Devs Offshore QA(s) Offshore BA(s) Onsite BA(s) This is how the communication works. Of course there are other exchanges that take place but the Business Q & A and the Technical Q & A are the most important pieces of concrete information exchanged. Other companies,… Read More »Onsite Business Analyst

Communication Patterns

Incidentally my earlier post was about how Distributed Agile works. My unexpectedly long web silence was infact due to the current DA project that I am working on. One interesting thing that we get to observe is how the communication patterns change over time, amongst the local team and also with the distributed team. There are few specific things that I have observed during the last 5 months on this project, which I would like to bring up here. All of these relate to the communication that happens across oceans. OverviewLast few months I have been busy on a Distributed… Read More »Communication Patterns


So what happens to the agility when the project is distributed? Well, it suffers… It’s not that it doesn’t work in a distributed context. In fact ThoughtWorks has been doing distributed agile for quite sometime now. We talked about some of the best practices of agile earlier. Let us see what problems distributed agile poses to these principles. Time differenceWhen working across oceans, the first thing that hits the team is the time difference. The typical arrangement renders the team to be in a low cost country like India and the client in the US of A or Europe. The… Read More »Overseas…