Anecdotal Use Case: Using Google Wave for a Live Design Document
The following anecdotal use case is by David Mark Byttow, a software engineer at Google and member of the Google Wave team:
It should come as no surprise that Google Wave serves as our primary means of communication within the Google Wave team. We typically only use email for backward compatibility with other systems and/or teams that have not yet moved entirely onto Google Wave. We often talk amongst the team about “Wave moments,” or unique moments that highlight the power of real-time communication and the Google Wave platform.
We use Google Wave for various types of use cases for which email is not a suitable solution, including design documents, team updates, virtual meetings, topical discussions, prescheduled office hours for developers in our sandbox, and much more. One of my most memorable Wave moments was the creation of a technical design document for an internal system that is used to support Google Wave’s extension features.
I began by creating a new wave aimed at constructing a rough technical sketch of what I had determined as the primary goals, requirements, implementation, and open issues that should be addressed. I then added colleagues who have the domain-specific knowledge on the various topics that I had prioritized and that I wanted to be discussed. I added relevant questions for each individual and added them to the wave.
Blips began to appear within minutes, and the wave lit up with cursors as each ...