It always amazes me that after project managers put so much time and effort into creating a baseline project schedule, they do not always put the same level of energy and discipline into maintaining it during the execution phase of the project.
It is extremely important during this phase of the project that the schedule reflects where you are at currently, as well as how the remaining work is planned to be completed.
A productive project manager will ensure that these update processes are linked to other project related activities, such as time reporting, team meetings, and status reporting.
Note − With MS Project 2013, you can save up to 11 Baselines in a Single plan.
These multiple baselines seem contrary to the definition of baseline.
In addition, these processes should be timely and consistent.
The updates should be completed the same time/date during the reporting period (day/week).
The approach helps focus in on specific problem areas: Most likely you will have run across the answer to this question when gathering progress updates from team members.
If not, this is a good opportunity to follow-up with team members on the status of specific tasks.Team members should KNOW when information is due and when the schedule updates have been completed.Based upon the organization and work environment, the project manager either establishes formal or informal processes and tools to collect progress updates.Resistance to formal tracking of project management data is normal.You can overcome resistance to tracking by explaining your expectations, explaining the benefits of tracking, and training people to track the task themselves.You have several options for the same − An interim plan saves only two kinds of information for each task − Current start dates and Current finish dates. It is visually easy to see how off-track or on-track the project progress is.