As a general rule, I would check once a week. Living in the real world where I work with real people... I have learned that some people I can mostly leave alone, some people I can check with once a week, and some who need more personal attention. Saving Changes...
The answer depends on the current stage of the project (red/yellow/green). Usually once a week is good enough but if the project is off the schedule, a more frequent checks for slippages, resource balancing and to removing dependencies may be necessary. I've been in two projects that are entirely opposite. In one project we checked the schedule once a week and in another project we had a WAR room set up to track the progress on hourly basis.
...
1 reply by Riyadh Salih
Jan 28, 2019 3:12 PM
Riyadh Salih
...
Venugopal, good point and I agree that sometimes we need to check more often more than once a week
yes, regular on a daily basis (team stand-up meeting).
...
1 reply by Riyadh Salih
Jan 28, 2019 3:14 PM
Riyadh Salih
...
Peter, I thought that daily stand up meeting is short for max. ten minutes to check over all not specific to schedule compliance unless there is an issue which might disturb the schedule.
It depends on the duration of the project, the degree of control desired and the level of detail within the schedule.
Very short duration, time critical projects might require daily checking whereas schedules for mega-projects could be checked much less frequently.
Kiron
...
1 reply by Riyadh Salih
Jan 28, 2019 3:18 PM
Riyadh Salih
...
Kiron, I agree with you I noticed that it might need daily for some situation or special projects however if everything within controlled common cause variance then yes once a week is good enough, otherwise like you mentioned the criticality can play big part.
It has to do with the nature of the project, the history of the team, the phase of the project lifecycle, etc.
...
1 reply by Riyadh Salih
Jan 28, 2019 3:20 PM
Riyadh Salih
...
Aboalfazi, yes I agree it all depends on the situation but I believe in general weekly is a good practice otherwise many times we missed that one too and caused lots of regrets later on.
The answer depends on the current stage of the project (red/yellow/green). Usually once a week is good enough but if the project is off the schedule, a more frequent checks for slippages, resource balancing and to removing dependencies may be necessary. I've been in two projects that are entirely opposite. In one project we checked the schedule once a week and in another project we had a WAR room set up to track the progress on hourly basis.
Venugopal, good point and I agree that sometimes we need to check more often more than once a week Saving Changes...
yes, regular on a daily basis (team stand-up meeting).
Peter, I thought that daily stand up meeting is short for max. ten minutes to check over all not specific to schedule compliance unless there is an issue which might disturb the schedule.
...
1 reply by Peter Ambrosy
Jan 29, 2019 2:39 PM
Peter Ambrosy
...
Max 15 minutes. In that 15 minutes you hear a lot of things that give you a first-hand impression whether you are on schedule or not, especially when team members start repeating themselves or using most of the time to highlight impediments.
It depends on the duration of the project, the degree of control desired and the level of detail within the schedule.
Very short duration, time critical projects might require daily checking whereas schedules for mega-projects could be checked much less frequently.
Kiron
Kiron, I agree with you I noticed that it might need daily for some situation or special projects however if everything within controlled common cause variance then yes once a week is good enough, otherwise like you mentioned the criticality can play big part. Saving Changes...
It has to do with the nature of the project, the history of the team, the phase of the project lifecycle, etc.
Aboalfazi, yes I agree it all depends on the situation but I believe in general weekly is a good practice otherwise many times we missed that one too and caused lots of regrets later on. Saving Changes...
