Your Status Meetings quickly earn a reputation, and it’s usually bad. First we’ll discuss three types of bad status meetings. Then we’ll explore ways to make your status meetings short and effective.
Status Meeting Types
Status Meeting Organization
You can fix the problem with whatever type of status meeting you have by learning how to organize your status meetings. We all have heard these statements: What is the purpose of meeting every week? Don’t we have enough meetings? We project managers have asked ourselves this question: How can we organize a status meeting that gets results and doesn’t bore people to death? Lately I’ve tried something that takes a little more work on my end but boosts the productivity of my status meetings. It also cuts down the time that status meetings take. Let me tell you what worked for me… How to Write a Weekly Status Report
First, I prepare the agenda for the project status meeting ahead of time. Let me explain. What is the purpose of the status meeting? It is to provide your team with the overall status of the project and to learn the status of their activities. It is also to identify potential problems. The emphasis is on identification, not on solution. So I prepare a standard project status report meeting form. That sounds bureaucratic, but it isn’t. The first section just lists the people who are expected to show up and those who are not. Those who are not expected to show up, will receive the meeting minutes. Next, I add a graph about the project status. For this status I graph the information from my Earned Value Analysis. It shows a comparison between the percentage of work actually completed vs. the percentage of work planned to be completed. Next, I add sections for activities that are overdue, that are due this month, and that are active throughout this month. For each activity, I list only the following information:
- The owner of the task
- The original due date
- The current estimated completion date
- The current % complete
- Three lines for status text
Every week, I update the status for each of the tasks according to the status reports I received throughout the week.
Second, I organize the meeting using MS Outlook’s meeting organizer. I know it sounds trivial, but I need to make sure people know there is a recurring status meeting.
The actual meeting follows a simple routine. We discuss what’s new on the project. Next there is a general status report of the project, followed by a status update of each of the tasks listed. Going through the task list is rather simple. I state the task and ask the task owner where they are on the task. I do not go into details during the status meeting. I don’t want to start lengthy discussions. If I sense a problem, I will schedule a private meeting with the task owner. Going through the task list usually takes no more than 20 minutes. Once this is done, I ask the team if there is anything else we should add to the protocol. Once again, my goal is not to solve all these issues. It is to bring topics to the table and organize additional meetings for the problem solving process.
Lastly, I make sure that the updated meeting protocol is available for everyone to view no later than 48 hrs. after the meeting.
Using this method, the time spent in status meetings went down to about 30 minutes, just enough to keep everyone focused.
If your team has problems with the status meeting, try structuring the meeting in a similar way. By doing so, you provide a protocol and agenda that you can enforce. And you actually boil down the meeting’s purpose to what it is: Getting a status, not solving all problems and issues.
Learn how to lead effective project status meetings in our online project management basics courses. You work privately with a expert project manager and practice running meetings in live online conferences, just the 2 of you. You control the course schedule and pace and have as many phone calls and live video conferences with your instructor as you wish. Take a look at the course in your specialty.
[button link=”http://126.96.36.199/~jwkdwgmy/it-project-management/it-project-basics-111/” style=”info” color=”red” window=”yes”]IT Projects[/button]
[button link=”http://188.8.131.52/~jwkdwgmy/business-project-management/project-management-basics/” size=”medium” style=”download” color=”#1e14a8″ border=”#940940″ window=“yes”]Business[/button]
[button link=”http://184.108.40.206/~jwkdwgmy/construction-project-management/construction-project-basics-121/” style=”info” color=”red” window=”yes” bg_color=“00000000″]Construction[/button]
[button link=”http://220.127.116.11/~jwkdwgmy/healthcare-project-management-2/healthcare-project-basics-131-2/” style=”info” color=”#1e14a8″ window=”yes” bg_color=“00000000″]Healthcare[/button]
[button link=”http://18.104.22.168/~jwkdwgmy/client-project-management/client-project-basics-online-141/” style=”info” color=”red” window=”yes” bg_color=”00000000″]Client Projects[/button]