Please Share Feedback

Questions, comments, suggestions? Let us know what you think on our Forum.

To contact us privately, please use our contact form.

Author: Elyse, PMP, CPHIMS
December 18, 2008

He who hath the money hath captivated the audience.

It has been a while since I posted. Too long in fact. So in considering what to share, I decided to discuss improvements to our project bulletin board. We have been diligently maintaining and distributing a project bulletin board for the last year. There are some lessons learned.

First, when drafting up the bulletin board, talk to your executives regarding the information to be shared. Assure there is a common understanding of the information and its relevancy.

Next, be certain to have a high level project budget numbers as a part of the reporting summarization. For example, knowing how much money has been spend to date, and the estimate to complete is valuable. It makes sense to include salary information for the individuals doing the project work also.

Another item to share is have a process or a way to clearly distinguish a project from a work order from a repeatable operational request. I've found as individuals struggle with the project concept, they substituted the define project management process to manage work intake for all work. It is unreasonable to create a business case for a software update which only entails updating the push package and testing it.

Have a review process of the status report, including the leadership team. Enlighten the project managers whose updates have been poor quality or non-existant on the consequences of their actions. It may take time to find a consequence which is concerning to the project manager.

Finally, beware of passive agressive resistance, some small recommended changes lead to significant reporting problems.

Begin with subjective criteria for spotlightening status. Have a formal plan to develop that criteria into clear objective criteria.

Remember, a yellow project highlighting risks may raise and continue to illustrate constant awareness.

Assure changes to the process after implementation are communicate at least eight different ways.

These are a couple of my lessons learned, I wanted to share. If you have had a similar experience, please feel free to share letting us know what worked and what didn't.

If you enjoyed this post, you may also want to check out:

Subscribe and Share!

Did you enjoy this article? Your feedback is very important! I'd like to invite you to keep up to date with the latest posts from Anticlue. We offer several venues. If you have some questions, help can be found here.

1 Comments to “Project Status Reporting Lessons Shared”

Interesting Post!!!
All information is really useful and the article is conscise and clearly understandable
It is very important to know what is the Project Status and mainly everything what it involves.
So I fond not only this post so interesting but also the whole blog!

« Imagine the possiblities - BI impact on revenue cycle operations A Marketing Campaign: The Problem Solving Walk-About »

Please share your thoughts and suggestions