Project management does not exist in a vacuum. We have embraced the various new methods of communication to encourage better collaboration and team-work. It is now practically inconceivable for a project not to be using email, tele-conferences, even video-conferencing to maintain contact with the participants.
But are we embracing the new technologies available now? Are we making best use of the tools we now have? With project teams becoming even more spread out over the globe, are we making best use of our new communication methods?
This series will look at the various new social media tools available to us, and how we can start to use them in our projects. Some of you will already be using some of these tools. I’d love to hear your stories about how they have worked for you – many of the uses are only now developing, so I’d love to hear your best practices!
Wikis are websites that allow the people who access it to contribute to it, or to change and update the information that is already there. The most famous example of a wiki has to be, of course, Wikipedia, which has harnessed the efforts of individuals around the world to build a resource with a remarkable breadth, though with sometimes variable quality!
But can a similar system be of use to us as project managers? We’ve already looked at the benefits of FriendFeed, most notably that as all the ‘conversational’ information is being captured, it generates a searchable resource of this information. However, sometimes we need to make things more formal.
While we can use blogs to share formal documents, they are primarily a one to many communication tool, in that the person writing the posts has the most control over putting information out. In other words, while a blog is useful for gathering comments on the information, it is not good at allowing collaboration in the creation of it.
When all of your team are close by, this may not be a problem – you can walk over and talk to them! Unfortunately, this is increasingly often not the case, and this is where a wiki can come into its own.
By putting up a wiki page, you enable the people viewing it to add information, to modify what is there, and to improve the usefulness of it. This means you can gather the knowledge and expertise from all of your team members, who can contribute to the generation of this resource.
This is useful when you are looking not only at the documentation around running the project, such as risk logs, but also when you are looking to create the documentation about the product – in other words, the documentation about using the product, which should be part of the output of the project.
A wiki isn’t the perfect answer, of course. While, hopefully, the documentation produced on the wiki will be good, it still needs to go through a quality process before release, and this may uncover problems. And, of course, actually getting your team to contribute needs discipline on both your and their parts. There may be a temptation to set up a wiki and leave it alone, assuming that the documentation will magically now get written. This works about as well as you would expect.
But while a wiki brings some challenges, the benefits of using one can be great. Having the accumulated knowledge and expertise of the project team around this project put down in an organised manner is incredibly valuable. And if it is done throughout the life of the project, it is likely to be much more successful than when tacked on the end.
Have you used a wiki in project management? Was it useful? Or did it just mean another thing that had to be monitored? What do you think? Let me know!