Research proves that the word ‘status’ is used a million times during the course of a project by a Project Manager.
Okay, I’m just kidding! But, you get what I mean. Many a times, it feels that a project is running on the heels of status reports. A status report appears to be that core element which is the centre of focus all the time, sometimes even more than the actual code or the product.
In the world of global and huge sized project teams with sub-teams focused on disparate aspects of the project and a senior management that is paranoid to stay on top of everything, status reports seem to be the enabler and the preferred choice of communication.
So, it becomes important to look at some of the details that are laid out in a status report. Here are 5 common pitfalls that most Project Managers tend to fall into while writing a status.