SOLVED

Automatic task escheduling without restrictions?

Brass Contributor

Hello

I have a certain problem in my schedule, where I have already carried out the planning, created the baseline and am in the control stage. There have been several delays, the project I am working on is being directly impacted by weather conditions.

 

Therefore, a task that was scheduled to take place on 01/30 has not yet started. And my question is, why does MS Project not update my date to the nearest day (today)?

 

Look below:

 

FernandoFalchiane_0-1707249905185.png

FernandoFalchiane_1-1707249983366.png

Column Green: Baseline 1

Column Blue: Baseline 2

 

5 Replies
FernandoFalchiane,
What exactly do you mean by, "update my date to the nearest day"? Are you expecting Project to automatically change your schedule based on the current date?

Your screen shot shows two baselines (Green and Blue). Why did you do that?

John
Exactly, I have a baseline for my project, if I don't have real dates, my input table will show my baseline, as we progress through the project stages, at some point I will have a mix between estimated dates and actual dates, right? Shouldn't MS Project change my estimate as the day goes on for tasks that haven't been started yet?

But back to the schedule, the columns are the differences between the project baselines, the third set of columns are the actual dates.

So, in order for me to be able to effectively control my schedule so that no activity is delayed, if the day arrives and it hasn't started yet, should I manually change my baseline?

Please tell me if I managed to explain it in the best way.
best response confirmed by FernandoFalchiane (Brass Contributor)
Solution
FernandoFalchiane,
I'm afraid you have a misunderstanding of what a baseline is. A baseline is set to capture the original plan in a group of baseline fields (i.e. Baseline Start, Baseline Duration, Baseline Cost, etc.). Those baseline fields can then be used to compare the current schedule fields with the original plan. Normally a baseline is set at the beginning of a plan before execution starts and is not changed unless there is a change in scope (e.g. tasks added/deleted). Under certain circumstances, it may be desirable set one or more new baselines if the current plan has changed considerably from the original plan.

The "estimated" dates you refer to is what makes up the current schedule. The current schedule is dynamic. As the plan is executed task dates and durations will change in response to reality (i.e. tasks get delayed, tasks finish early, the sequence of tasks may change, etc.). Actual dates are entered via the Actual Start and Actual Finish fields if tasks do not start or finish on their scheduled dates.

The current schedule dates and actual dates have nothing to do with baseline dates. The current schedule dates for tasks that have not started, and actual dates for tasks that have started and/or completed represent the current plan. The baseline represents the original plan.

You "control" your schedule by tracking progress (e.g. actual work, remaining work) and adjusting the plan (i.e. revised estimates of work, adding/removing resources, changing the logic sequence of tasks, etc.). That's called managing the project.

Hopefully this clarifies more about how Project works.

John
What you mentioned makes a lot of sense, in fact I was controlling the schedule very lightly.

I crossed the posts I didn't know they were the same members, but I needed a very quick response given my current situation. It won't happen again, thank you very much, I marked it as best answer.

@FernandoFalchiane 

You're welcome and thanks for the feedback.

 

John

1 best response

Accepted Solutions
best response confirmed by FernandoFalchiane (Brass Contributor)
Solution
FernandoFalchiane,
I'm afraid you have a misunderstanding of what a baseline is. A baseline is set to capture the original plan in a group of baseline fields (i.e. Baseline Start, Baseline Duration, Baseline Cost, etc.). Those baseline fields can then be used to compare the current schedule fields with the original plan. Normally a baseline is set at the beginning of a plan before execution starts and is not changed unless there is a change in scope (e.g. tasks added/deleted). Under certain circumstances, it may be desirable set one or more new baselines if the current plan has changed considerably from the original plan.

The "estimated" dates you refer to is what makes up the current schedule. The current schedule is dynamic. As the plan is executed task dates and durations will change in response to reality (i.e. tasks get delayed, tasks finish early, the sequence of tasks may change, etc.). Actual dates are entered via the Actual Start and Actual Finish fields if tasks do not start or finish on their scheduled dates.

The current schedule dates and actual dates have nothing to do with baseline dates. The current schedule dates for tasks that have not started, and actual dates for tasks that have started and/or completed represent the current plan. The baseline represents the original plan.

You "control" your schedule by tracking progress (e.g. actual work, remaining work) and adjusting the plan (i.e. revised estimates of work, adding/removing resources, changing the logic sequence of tasks, etc.). That's called managing the project.

Hopefully this clarifies more about how Project works.

John

View solution in original post