Here is the situation. The project is baselined and is in execution. Mid-way through the project, there is a negative schedule variance of 5 days (the project is 5 days behind schedule). At this point, the customer asks for a change which adds 10 days to the Baseline Duration. I have created a new baseline to incorporate the change request. However, when I review the new baseline, the original 5days of duration variance has disappeared. What is happening in MS Project and how should this be handled – a) to continue to reflect the 5 days negative duration variance and b) to accommodate the change request.
The proper way to maintain a baseline for this situation is to add the additional tasks for the chage, note and tasks that have been extended as a result of the change, select those tasks, set baseline for selected tasks, and rollup baseline to summary tasks. You should do this to your current baseline (not create a new baseline). This process doesn’t specifically itemize the tasks that were part of the original variance vs the tasks that were reflected by the change request but that can be managed through a custom descriptive field. But, those tasks already started are part of the original variance and those future affected tasks are included in the change request. Hope that helps…
I always keep a copy of the original schedule, including the original (agreed) baseline (and copies of subsequent client agreed changes).
Then I make a copy of the original (or current) baseline. Add the client changes to that version (untramelled by the reality of a 5 day slip). I usually add them at the end of the tasklisk under the heading Change Requests. In your current schedule:
Copy/move your current baseline to Baseline 1 (or Baseline n – depending on how many changes you client has asked for since you began).
Copy across the change request tasks.
Copy across the changed Baseline.
Thanks so much! Let me try this.