Agile Zone is brought to you in partnership with:

Mark is a graph advocate and field engineer for Neo Technology, the company behind the Neo4j graph database. As a field engineer, Mark helps customers embrace graph data and Neo4j building sophisticated solutions to challenging data problems. When he's not with customers Mark is a developer on Neo4j and writes his experiences of being a graphista on a popular blog at http://markhneedham.com/blog. He tweets at @markhneedham. Mark is a DZone MVB and is not an employee of DZone and has posted 544 posts at DZone. You can read more from them at their website. View Full User Profile

Distributed Agile: Other Observations

12.17.2010
| 2318 views |
  • submit to reddit

Some of the difficulties of working in an offshore environment were clear to me before I even came to India but I've come across a few others lately which I either didn't think about before or didn't realise how annoying they were!

Getting data from the client's network

For several of the stories that we've been working on lately we needed to make use of huge amounts of reference data residing on the client's network.

If we were working in the same building then it would be very quick to download that and use it for whatever we needed.

Working offshore we've been downloading those dumps via scp which can take around 5 hours for a 300 MB file.

I don't know a lot about networks but I'm told that it would be possible to create a direct VPN between our office and the client's which would allow the transfer of this type of data to be much quicker.

Dealing with internal IP addresses

Since we're working on a different network any IP addresses for test environments of external systems aren't directly accessible.

We have a box setup in our office connected via a VPN to the client's network which forwards requests we make to local IP addresses to the equivalent IPs on the client's network.

There have been several occasions when there have been internal IP addresses hard coded in our configuration files and we've completely forgotten that we need to create an equivalent local address.

It's not a big time waster but it's something you wouldn't have to think about if working in the client's office.

Slowness of the feedback cycle

It's obvious that if the client is in a different country to you that there will be less face to face communication but I didn't realise how frustrating that would be.

If you have an observation about a piece of functionality and the offshore BAs don't have the answer then you'll most likely have to wait 5/6 hours to speak to someone onshore about it or write your thoughts in an email.

While both of those are viable options I find my motivation to express my opinion is much lower if I can't get feedback straight away.

As a result of this communication lag I think that we spend more time building functionality which doesn't necessarily add a lot of value.

 

From http://www.markhneedham.com/blog/2010/12/12/distributed-agile-other-observations/

Published at DZone with permission of Mark Needham, author and DZone MVB.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Tags: