Project progress reports

In general the prevailing opinion about project progress reporting focuses on two things:

• the importance of keeping reports succinct
• the importance of understanding the information needs of the different stakeholders

After analyzing the reporting requirements in their architectural/construction company, project managers M. Abdomerovic, G. Blakemore, and J. Stewart (2000) found the following results:

They also found that the work breakdown structure (WBS) is the most effective tool in providing a baseline for reporting project progress. If stakeholders have access to the WBS, they can better put the project progress reports in context, and the reports can be more succinct.

According to Abdomerovic et al., "reports can be shown simply, even though the structures that create the basis for reports could be numerous and complicated" (30).

Since stakeholders are more likely to read and respond to project progress reports when they are succinct, as a project manager you are more likely to get credit for your work and get the support you need on your project. When a project status report is too long, your sponsor or your boss is more likely to forget the information and therefore forget who did the work. Furthermore when a project stakeholder is clear about a project and its progress, he or she is more likely to support it. As Katherine Spencer Lee, executive director of Robert Half Technology, says, "one of the most useful ways to stay on the radar is through weekly project status reports. . . . Are you keeping them brief and straightforward, so your manager actually has time to review all of your accomplishments?" (39).

As far as the specific information that should be provided on project progress reports, current theories are very consistent. Most of the literature is general about what information should be provided. Gantthead.com, a popular resource for project managers, provides this list of the elements that should be included: