Nari Kanan from SourcingMag talks about the lack of iteration in offshore IT work:

However, (offshore) software development has institutionalized non-iterative ways of doing things. You CAN come up with a definitive requirements document that CAN be turned into a definitive design document that CAN be turned into perfect code, which in turn makes users ecstatic! Couldn’t be further from the truth.

Definitely. But how do you organize a successful, iterative process with an offshore team? Time & geography are the obvious challenges. But, the problem goes much deeper than that. It is about mindset. And, although your business development guy won’t admit it, his offshore team doesn’t have it.

Most offshore developers have never really been included in a brainstorming session or a scoping process - their job is about one thing: take requirements and churn out code. Now, we need them to learn to iterate. They haven’t even spent time scoping!

Successful iteration isn’t about reworking your code 14 times a month. When most offshore firms talk about iteration, what they really mean is that their project managers are going to rewrite requirements over and over again, guiding their developers through a series of protracted, stressful waterfall processes until everyone loses their mind.

14 waterfalls don’t make a river. They just make a lot of noise.

When we first started embracing iterative development 4 years ago, it just meant that we didn’t sleep. We would work with the client during the day, stay up with our team to communicate scope at night, and then get up early to synch everyone up and ‘iterate’ in the morning. Think that’s scalable? Ask my wife.

No, true iteration requires a reworking of the entire offshoring process. More on this soon.