Team blogs. Project aggregators and RSS feeds. Individual blogs.
Blog your thinking as you scope the project. Blog flash reports.
Meeting minutes. Task notes. Use a blog-to-email gateway for
stakeholder communications. Socialize new project members faster and
more completely. Create better after action reports.Projects often fail due to poor communication. Blogs aren’t a magic
pill, but they are a fast and cheap way to produce more and better
communication. More, because blogs lower some of the barriers to
communication and create personal and peer reinforcement for
sharing. Better, because blognets’ social nature also improves the
quality and context of those communications. The PMBOK describes a
basic project communication; you can live it with blognets.
I’m a wiki guy myself, Phil.
{ 0 comments… add one now }