One-Page Project Status Report; Keeping it Brief

There's a great writeup in Projects@Work about project status reports, including tips on meeting format and frequency as well as a format for a one-page status report.

According to the article, there are 5 Project Status Best Practices:

1. Consistency — The status process should be basically the same for large and small projects, and consistent with their measures of success
2. Escalation — The status process provides a mechanism for escalation of key issues.
3. Simple — One page with the ability to drill down for details when necessary
4. Public — Status is available to all (as appropriate) in order to communicate issues, risks and corrective action measures
5. Inclusive — All projects are required to provide status on a consistent set of metrics

For busy managers who see loads of project status reports, it's much easier to have a consistent, brief summary of what's really happening on each project. They don't need a dissertation on all the details, nor will they get a clear picture just looking at performance metrics. Much like on a business case, most just want the executive summary. Simpler is better. Less is more.

For those looking to improve their status reports (and their credibility with management), read on...

http://www.projectsatwork.com/content/Articles/231704.cfm