Mike, thanks for the presentation. One comment though: just because the activity is on the critical path doesn’t mean total float is zero. We can define total float for the critical path in P6 settings to any number of days.
I disagree. You just identified some cons to the Must Finish By. You didn't identify cons to the Finish on or Before method. A better comparative analysis would be preferred. I don't believe there should be a hard-set rule on saying don't use the Must Finish By as there are many different schedule types. Say for instance we had a large schedule 30k activities with multiple paths that were close in duration to the longest critical path. Then one of them extends out past the current critical path that you set a Finish on or Before constraint on. You won't see negative float where you should on the new critical path. Whereas with the Must Finish By you would. Maybe a few processes should be put into play before entering in a Must Finish By. 1. Enter in a Must Finish By only after the schedule is set before the 1st update. 2. While entering in the Must Finish by change users preferences to show time so that the correct date and time is selected. Negative float isn't necessarily bad. It's good because it's an indicator to let us know to pay attention to the schedule and get it back on track. No one want's a schedule that's behind, but we also do want good indicators to let us know when that happens. On a complex schedule the Finish on or Before may not cut it.
Thanks, Mike. I have never used it since my original P6 trainer advised me to avoid Must Finish by. I could not quite understand when you made an example increasing the duration of one critical path activity and then you re-scheduled and the total float changed from zero to -3. You said that it is not what it suppose to happens when you increase a duration (Minute 3:33) butI am confuse now. If you have an activity in the critical path with an specific duration and zero float, if you increase the duration, should not the total float become negative + the amount of days you increase the original duration of the acivity?
That -3d was the same in either method, the difference I guess was in cutting the duration. I still don’t get it: a 15d critical activity with zero float and you reduce the duration by 8d, so it should show 8d positive float.
Need to learn P6? Check out the best Advanced P6 Training Available online:
www.planacademy.com/
Mike, thanks for the presentation. One comment though: just because the activity is on the critical path doesn’t mean total float is zero. We can define total float for the critical path in P6 settings to any number of days.
Thank you so much Michael . This is a very important information for planners. Much appreciated for your awsome problem solving attitude.
Thank you so much Michael . This is a very important information for planners. Much appreciated
Thanks for sharing this Michael. Learned something from this video.
Thank you so much Michael , i was wondering on it
We're still awaiting for the BMW performance driving lessons :)
Many thanks Michael, very informative, perfect ☑️
Many thanks Michael , great
I disagree. You just identified some cons to the Must Finish By. You didn't identify cons to the Finish on or Before method. A better comparative analysis would be preferred. I don't believe there should be a hard-set rule on saying don't use the Must Finish By as there are many different schedule types. Say for instance we had a large schedule 30k activities with multiple paths that were close in duration to the longest critical path. Then one of them extends out past the current critical path that you set a Finish on or Before constraint on. You won't see negative float where you should on the new critical path. Whereas with the Must Finish By you would. Maybe a few processes should be put into play before entering in a Must Finish By. 1. Enter in a Must Finish By only after the schedule is set before the 1st update. 2. While entering in the Must Finish by change users preferences to show time so that the correct date and time is selected. Negative float isn't necessarily bad. It's good because it's an indicator to let us know to pay attention to the schedule and get it back on track. No one want's a schedule that's behind, but we also do want good indicators to let us know when that happens. On a complex schedule the Finish on or Before may not cut it.
Thanks you helped me
Thanks for making such an amazing content.
Good information 😊👍
Thank you
Thanks, Mike. I have never used it since my original P6 trainer advised me to avoid Must Finish by. I could not quite understand when you made an example increasing the duration of one critical path activity and then you re-scheduled and the total float changed from zero to -3. You said that it is not what it suppose to happens when you increase a duration (Minute 3:33) butI am confuse now. If you have an activity in the critical path with an specific duration and zero float, if you increase the duration, should not the total float become negative + the amount of days you increase the original duration of the acivity?
That -3d was the same in either method, the difference I guess was in cutting the duration. I still don’t get it: a 15d critical activity with zero float and you reduce the duration by 8d, so it should show 8d positive float.
How can I remove this project must finish date?
From the Projects screen, you'll find it on the Dates tab. Just erase any date in the field.