On Thu, Dec 3, 2009 at 11:37, Jonathan Christensen <[email protected]>wrote:

> Is anyone on this group finding utility in Google Wave?  If so, I'm curious
> to know what you're using it for.


I'm using Wave for a couple things. One is just for general brain-dump
rough-draft writing. Its outlining is decent and having some kind of
versioning makes me feel more comfortable with aggressive editing.

Probably the more interesting use case of mine, though, is using a Wave as
the backlog for a project I'm on with a remote team. Wave has many of the
good characteristics of a scrum- or kanban-style task board.

1. A wave is a shared, central, visible point of reference. We can all pull
up Wave and know that we're looking at the same version of the same content.
When we have planning meetings, we can pull up the backlog wave and run down
the list one item at a time.

2. Changes show up immediately, which gives us more incentive to change and
update and edit in real-time as we're talking. We add replies like you'd add
stickies to a white board, and nobody has to collate a bunch of notes later
(which nobody really ever does anyway, at least not very well).

3. It's easy for people to make their own changes and additions without
having to worry too much about explaining to everyone exactly what they
changed. Wave makes changes really visible on its own – I can see as soon as
I open a document what's new since the last time I looked at it.

So that's been working out pretty well for us. So in my case, Wave hasn't
replaced email by any means, but it has replaced some of my use of Google
Docs. As far as development task trackers goes, I just haven't really found
a setup yet that has made me want to ditch stickies on a whiteboard. Google
Wave is getting close-ish for this particular project, but even then I'm
still using sticky notes on a whiteboard to track these tasks when they
leave the backlog.

I'm also curious if anyone else out there is using Wave on any kind of
multiple-times-weekly kind of basis…

-- 
Nick Zadrozny

-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby

Reply via email to