Must Start on
- Created
- 1
- 4
Hi Planners,
A baseline schedule showing that the start date of the project "milestone task" is not critical "9 days float", some of the succesor tasks has a constraint "start no earlier than". I changed the constraint of those successors to "Must start on" and I got the start date critical. Is there any explanation to this?
Regards,
1 reply
Oldest first- 0Tom Boyle ·
Moutaz,Look closely at the
Moutaz,
Look closely at the early and late dates of your affected tasks.
- According to your description (and ignoring other impacts), at least one of your successor tasks already has a logic-driven early start date that is 9 days later than its SNET date.
- SNET constraints on the successor tasks only have the potential to affect their early dates - with no effect on your project start milestone.
- By changing the SNET constraints to MSO, you are completely over-writing both the early dates and the late dates on those tasks. The backward pass carries this effect back to the late dates of your project start milestone.
MSO/MFO constraints in MSP are similar to Mandatory constraints in P6. I avoid them in general. If Total Slack or the "Critical" flag is to be relied on, then you must never assign them to any logically-connected task. I wrote more about this last year: http://wp.me/p6CCB4-7w
Log in or join to reply
ProjectControls.com is free to join. Members can post questions, reply, vote and follow discussions.
Existing members: your original username and password still work. Forgot password?