By "Rapids Development," I mean "rapids" as in miniature waterfalls. Take standard waterfall development: Requirements > Specifications > Development > Test > Deploy. Then shrink it so that the entire cycle fits inside a six-month window. This will give you two of agile's biggest benefits -- namely, short delivery cycles and the reduced risk of project failure that comes with small size. And it will deliver them in a framework that lends itself to offshoring, shipping specifications to developers who use them to write code heads-down with no end-user interaction.
Is it ideal? No. Without a high-trust, high-contact environment to provide daily course corrections, and with a business analyst serving as a communications intermediary, the results will suffer a bit.
That's the price your company will pay in exchange for the lower cost per hour off its offshore developers.
This story, "Agile development + offshore jobs = a recipe for disaster," was originally published at InfoWorld.com. Read more of Bob Lewis's Advice Line blog on InfoWorld.com.