Paolo CornaliProject Manager| HTA srlBrescia, Lombardia, Italy
How do you perform the weekly update review of the projects?
At the moment I perform 1 to 1 interview with my colleagues verifying:
1) What they should have done in the past week
2) What they really done in the past week
3) Which problem they met
4) What they should do in the new week
I perform the interview with the timesheet of the past week close at hand and I update a visual to do list (one for each colleague) with sticky notes that include the following information:
1) task to do
2) priority
3) deadline
4) budget hours
5) actual hours
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Jan 13, 2016 12:13 AM
Replying to Paolo Cornali
...
Thanks for shared your point of view Rami.
You're welcome. I hope you found it useful. Saving Changes...
Anzor MisabishviliProject Manager| TD BankCherry Hill, Nj, United States
Jan 12, 2016 2:13 AM
Replying to Rami Kaibni
...
With respect to everyone's opinion, I tend to agree with Suhail on this. Don't waste too much time on analysis and 1-1 Interview Meetings, this could be done on daily basis through each section manager with his subordinates and/or through status reporting or other means on communication.
However, for large projects, I personally used to hold one weekly meeting with all section managers, stakeholders and client (I used to include the client YES because I always believe we are all on the same Boat):
Minutes of Meetings (MOM) where recorded: Concern / Action / Action By / Completion. Everyone of the PM Team Members knows their responsibility so next meeting we review the status of the items discussed last week and new items. An important thing, limit the meeting time to 1.5 HRS Strictly otherwise, you will open room for discussions where the sky is the limit. Always put rules and guidelines to your meeting: - Meeting Allocated Time - MOM Recorder - Meeting Leader - Meeting Agenda - List of Participants
I provided PMI recently with 6 Templates of which some are: MOM Format, List of Participants Format, Daily Report Format and Three Weeks Lookahead Schedule Format. When published, I will let you know so in case you need to use them, you will find them handy.
Definitely agree with Rami's feedback.
And an excellent idea to include the client in status meetings, when it is possible. Makes the client feel involved and appreciated. Usually ensures that the final product better aligns with client's requirements.
...
1 reply by Rami Kaibni
Jan 16, 2016 3:14 PM
Rami Kaibni
...
Exactly Anzor, this is what I've mentioned: All on the same boat, one team.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Jan 16, 2016 7:39 AM
Replying to Anzor Misabishvili
...
Definitely agree with Rami's feedback.
And an excellent idea to include the client in status meetings, when it is possible. Makes the client feel involved and appreciated. Usually ensures that the final product better aligns with client's requirements.
Exactly Anzor, this is what I've mentioned: All on the same boat, one team. Saving Changes...
Tiago MateusSenior PM | Author of the book "Project Your Life"| Volkswagen Financial ServicesPortugal
I would add and start with "risk discussions". And to avoid that some team members might feel sometimes the weekly meetings too repetitive, I would surprise them with something new each month (e.g., games, related articles and videos, outside meetings, ...).
What do you think about it?
...
1 reply by Paolo Cornali
Jan 20, 2016 12:35 AM
Paolo Cornali
...
Sorry Tiago but, IMHO, I don't think that is this the case. How I have specified in a previous post I refer to weekly update review with my peers in order to have an update of the status of the activities in progress. Consider that I manage a small interdisciplinary development team (mechanics, electronics, firmware, software) of 8 persons and about 5 or more projects in progress at the same time). The review it is like a small talk (10-15 minutes) and I think that add the things you suggest will make the review too heavy (consider that it is a weekly review). The things you suggest could be considered in a longer review.
Saving Changes...
Paolo CornaliProject Manager| HTA srlBrescia, Lombardia, Italy
Jan 19, 2016 8:18 AM
Replying to Tiago Mateus
...
I would add and start with "risk discussions". And to avoid that some team members might feel sometimes the weekly meetings too repetitive, I would surprise them with something new each month (e.g., games, related articles and videos, outside meetings, ...).
What do you think about it?
Sorry Tiago but, IMHO, I don't think that is this the case. How I have specified in a previous post I refer to weekly update review with my peers in order to have an update of the status of the activities in progress. Consider that I manage a small interdisciplinary development team (mechanics, electronics, firmware, software) of 8 persons and about 5 or more projects in progress at the same time). The review it is like a small talk (10-15 minutes) and I think that add the things you suggest will make the review too heavy (consider that it is a weekly review). The things you suggest could be considered in a longer review. Saving Changes...