This content has been marked as final. Show 4 replies
More information is needed to dismiss the obvious: that your last activity has been scheduled beyond the project's finish constraint date. Or that a task somewhere in the middle has done the same (probably keeping it 0 TF at the end). TF has no dependency on your baseline, so forget using that as the culprit.
Edited by: ITPM on Apr 9, 2012 7:04 PM
I recon you to check the constrains in the activities with negative floats. Next thing you can check is whether the task it resource dependent and you have allocated a resource with different calendar.
It is hard to give precise answer without details but hope above will be helpful.
How did you resolve your negative float issue?
Two options to reduce float:
1. Shorten the duration of critical path activities by adding more resources
2. Schedule sequential critical path activities to happen concurrently instead.