Agile Insider reality bytes…

Love Wave, Hate Google

I've not tried wave, but I'm already loving it, I can see immediately how it addresses one of my wishes from a previous post... But I'm hating the wait. I had always looked to Google as a very pioneering company and certainly assumed they applied agile principles. However, I can't see how such an important disruptive technology like Google Wave has managed to stay behind closed doors for 2 years...

I've been working on a few internal projects for my company of late and this has involved working in a distributed fashion (yes, pairing by phone), and during some of these sessions I can immediately envisage the benefits of using Wave.

Surely there is at least one complete, tested feature they can roll out to production?  My concern is there are still some fundamental challenges facing the team, and I would not be surprised to find it being concurrency issues, so as the potential end-user of this technology I'm going to make it clear, I don't particularly care about have multiple users editing the same document in real-time with transparent, asynchronous updating...  Let me edit, commit, refresh, etc as a simple starting point...  But whatever you do, let me do something before I find a simple alternative...

To find out more about wave, visit the wave site http://wave.google.com/, and especially watch the google I/O presentation...