in

 

Using blogs for project progress and, (semi-informal), status

Last post 03-28-2008 3:00 PM by emarone. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 03-28-2008 2:06 PM

    • sheaver
    • Top 500 Contributor
    • Joined on 03-28-2008
    • South Florida
    • Posts 2

    Computer [co] Using blogs for project progress and, (semi-informal), status

    Something I have been thinking about for quite a while is the use of blogs to facilitate project status and progress tracking - I'd like to hear any opinions, experience, thoughts on this.

    Blogging basically lets you build a project diary or journal that provides a great repository of information to build and support a summary report while also enabling anyone to view an up-to-the-minute description of how the project is coming along.

    A couple of reasons for contemplating the use of a blog are

    Weekly reports may not be timely enough...

    Example - If a project Manager reports the weekly status to their boss on a Tuesday, yet they report to their boss, (executives for instance), each Monday...the report will always be about a week late.

    When further detail is required...

    Example - Weekly status reports, (usually in a document fashion such as MS Word), are usually prepared by the Project Manager, and summarize the week's activities, milestones, issues etc... But if for some reason more detail is needed, the PM usually needs to scurry around getting this from project team leads and members.

    Different sources of information

    Example - in the majority of projects there are probably a number of teams working together but each providing their own status at certain intervals (weekly in most cases). The correlation and merging of these reports into one Status or Progress report can be time consuming.

    Solutions via a blog....

    In a blog scenario, the Project Manager and/or team leads could post the important happenings within the project on a daily or as-it-happens basis. Resolved issues with brief solution descriptions, escalated or new issues, risk activities, potential gotchas, vacations/sickness, etc....

    Most existing project management software is designed for people to enter data but not to interact and collaborate with each other on the project. A blog facilitates open dialogue as well as being a repository for concrete project progress information from various sources.

    Plus, most blogging applications allow people to subscribe via RSS and thereby these people have instant access to the latest project information as soon as it happens.

    I'm not saying to do away completely with formal project status reports...(yet)...but it's an interesting idea....

    Thoughts, comments, experiences, suggestions.......
    Shea Heaver, PMP
  • 03-28-2008 3:00 PM In reply to

    • emarone
    • Top 10 Contributor
    • Joined on 09-19-2006
    • Seattle, WA
    • Posts 268

    Re: Using blogs for project progress and, (semi-informal), status

    I really like the immediacy and collaborative capabilities that blogs offer, and I'm also finding wikis are increasingly common for sharing project knowledge as well.

    Although Daptiv doesn't have a true blog feature, it does have two project applications that offer some really nice collaboration capabilities:

    • News is the project "bulletin board," where team members can post one-off news items that don't require any feedback or discussion.  Any project member (with appropriate permissions) can post status updates, share project-related information, or post other comments at any time, where the formal Status Update function is only available for project managers.
    • Discussions is a little closer to blog-like functionality, although it is closer to an unmoderated forum, where a project member can post a topic for discussion and team members can reply in a threaded Q-and-A format, not unlike the forms here at the Daptiv Community.

    These have been some of the lesser-used functions in Daptiv, primarily because these are the kinds of communication needs people traditionally have used email for.  However, with collaborative technologies like blogs and wikis becoming more common, I've seen a renewed interest in these features within the Datpiv project space.

    Because these items are completely integrated with the Daptiv project information, it decreases the number of places project team members have to look for project information, and with the RSS permalinks available through the Daptiv global tabs, these features can be treated like any other blog or newsfeed.  You also have the item-level view restrictions and role-based permissions to limit which project team members can view the information stored in these applications.

    For any organizations that are currently using, or are exploring the use of, blogs or other collaborative tools to support project information sharing, I'd recommend taking a look at these simple and intuitive applications that already built into the Daptive solution set.

    Erik Marone | Daptiv Product Manager
Page 1 of 1 (2 items)

Navigate: Home | Blogs | Forums | Solution Library  Get Help:  Contact | Feedback | FAQ   Terms of Use:  Terms & Conditions | Privacy Policy