Phil Windley points out a nice bit by Jonathan Peterson describing why blogs are strong contenders for project managment:
Now lets look at a blogged IT organization:
- Each developer and/or development team would keep a project blog with RSS.
- The PM would subscribe to all those blogs and would publish a roll-up blog with links to details of various issues.
- The program manager would subscribe to the RSS feeds for every project or team that impacts his project portfolio and would publish his own blog.
- The Powerpoint deck would now have live links to blog entries at the program office level.
Peterson concedes blogging tools are not perfect for project management — doesn't track workflow well, hard to find complete thread of a subject, muddled distinction between internal and external communications— but are fixable. In his follow up to this, Peterson points out the most robust purpose of blogging is capturing verbal knowledge before it walks out the door: His strongest case for the corporate value of blogging:
The “war stories” exchanged by greybeards are not just a means of socialization; they are also a mechanism for passing down valuable information to the next generation. A google search across such "tales" would likely be invaluable in an organization like Nynex. So before you pooh-pooh corporate blogging, ask yourself —How much of your corporate culture is verbal and walks out the door at the end of the day?
Which reminds me to go update my project blog
Posted at July 24, 2003 11:23 AM