Our final project document was submitted last week with little fuss or fanfare. I have a feeling that most team members found the virtual teamwork experience and the work produced underwhelming. I know that the project manager found it frustrating, as did I and probably a few others.
A more comprehensive postmortem will be required, but a preliminary review of my previous posts show that my own frustrations seem to revolve around our reliance on email and discussion boards as our sole means of communication. Of course, this need not have been the case: we had a range of mediums available to us, from voice calls and video conferencing to specialist virtual teamwork platforms.
At the beginning of the project I suggested that a Skype call may be a good way to initiate the team. This suggestion was opposed by a number of teammates who felt that the time difference between Ireland and the Florida would prove too inconvenient: it never happened. My UL classmate and I also exchanged phone numbers, but neither of us made a call. The team leader did set up a Microsoft Office ‘groups’ account, but I was the only member to use it – on a single occasion.
We did use a Google Doc to submit work, and this platform has some good features. The different editing modes allow you to comment on, and suggest changes to documents. Email notifications let you know if a suggestion has been made or accepted/rejected. This was very useful. However, formatting in Google Docs was dreadful. This may have been due to the way we used the platform: no design specifications or guidelines were agreed upon, and everyone appears to have actually created their work in Word and just pasted into the Doc with its Word formatting attached. The results were more that unwieldy, they were montrous!
While I’m sure there are many other factors involved here, I do think that the way we communicated shaped the way we worked together, and the work we produced. By limiting our means of communication we also limited our scope for collaboration and our teams potential.
(Image: by GDJ, Open Clipart)