Welcome to Planning Planet. The majority of the folks on this site are practitioners of logic-based project planning and scheduling. In this regime, virtually all dates are OUTPUTs. The controlling inputs are volumes of work, activity definitions, durations, logical sequencing, and applied resources (including production rates). Inputting dates to the schedule - typically using date Constraints - has the potential to override the logic-based schedule calculation that leads to a more valid forecast of project outcomes. Consequently, it is best to restrict the application of the various types of constraints to only those cases where they are specifically required (and justified/documented) to meet project objectives.
In the blog that you linked, the writer advises planners to avoid making manual entries in the task Start and Finish fields in Microsoft Project schedules. That's because MSP automatically converts most such entries into date Constraints, destroying any pretense of logic-based planning and scheduling of the project. The advice is good for those seeking a logic-driven project schedule.
The approach you describe above is manual scheduling - it's what humans do. Instead of using the power of the computer to compute the dates and floats based on key inputs, you are estimating them in your head and skipping straight to the end. In effect, you are using MSP as a bar-chart drafting tool. Manual scheduling is intuitive, requires little effort, and can lead to perfectly adequate schedules for simple projects. MSP also makes it easy. If that's your world, then continue on.
Member for
18 years 11 monthsJohn,Welcome to Planning
John,
Welcome to Planning Planet. The majority of the folks on this site are practitioners of logic-based project planning and scheduling. In this regime, virtually all dates are OUTPUTs. The controlling inputs are volumes of work, activity definitions, durations, logical sequencing, and applied resources (including production rates). Inputting dates to the schedule - typically using date Constraints - has the potential to override the logic-based schedule calculation that leads to a more valid forecast of project outcomes. Consequently, it is best to restrict the application of the various types of constraints to only those cases where they are specifically required (and justified/documented) to meet project objectives.
In the blog that you linked, the writer advises planners to avoid making manual entries in the task Start and Finish fields in Microsoft Project schedules. That's because MSP automatically converts most such entries into date Constraints, destroying any pretense of logic-based planning and scheduling of the project. The advice is good for those seeking a logic-driven project schedule.
The approach you describe above is manual scheduling - it's what humans do. Instead of using the power of the computer to compute the dates and floats based on key inputs, you are estimating them in your head and skipping straight to the end. In effect, you are using MSP as a bar-chart drafting tool. Manual scheduling is intuitive, requires little effort, and can lead to perfectly adequate schedules for simple projects. MSP also makes it easy. If that's your world, then continue on.