Blogging on projects can be a great way to let folks know status of key tasks. I've used blogs to report progress towards key milestones, results of testing, and completion of key work products. The great thing about blogs is that when reporting progress, folks don't need to figure out who to send emails to and those people who don't want to get notifications any more can opt out of the alerting. Also, blogs provide a chronological history of the project - useful when having independent reviews or audits (or cya). Good use of blogs will also cut down on the number of meetings you'll need.
Here are some recommendations:
* Setup a blog for each project, assuming a project is around 2 months or more.
* Each person on the project sets up an alert on the blog so they'll get a notification when something is posted.
* For each deliverable, peer review, or formal review, make it part of the closure criteria to post.
* Include instructions on when to blog in the projects collaboration playbook. If the blogging tool you use allows for tagging, give some basic guidelines
* Blog postings should be simple - not lots of elaboration. Use links to supporting documentation.
Here are some recommendations:
* Setup a blog for each project, assuming a project is around 2 months or more.
* Each person on the project sets up an alert on the blog so they'll get a notification when something is posted.
* For each deliverable, peer review, or formal review, make it part of the closure criteria to post.
* Include instructions on when to blog in the projects collaboration playbook. If the blogging tool you use allows for tagging, give some basic guidelines
* Blog postings should be simple - not lots of elaboration. Use links to supporting documentation.
Posts
