Project Status Reporting – A Radical (?) Approach


mec. musings

Business sponsors know what they are “expected to expect” from a project status report.  Likewise, most project managers know what is “supposed to be” in a status report.  While much of this standard information is relevant, oftentimes status reports can be less about “information I need to do my job” and more about “information that, by God, is just supposed to be in a project status report!” (optional ‘harrumph’).  We don’t produce status reports to satisfy the Gods of Project Management; we produce status reports to communicate information relevant to the business sponsor.

With that in mind, I’m going to propose something radical here.  Rather than start with a template approach, I’m going to propose that the project manager sit down with the business sponsor and ask a few simple questions, such as:

  • After you read the status report, what do you need to be able to do?
  • What information…

View original post 286 more words