I'm reviewing an MSP programme for a colleague. He is concerned that he can't see a critical path running through the project schedule.
The "critical" filter shows the back end of the path, but not any activities upstream of a critical SS + lag relationship
I think this is because MSP is calulcating total slack (aka float) as finish slack, rather than finish or start slack, whichever is lower.
Is there a setting I can change, so that it will take start slack into account for criticality?
Obviously, I can suggest that he replaces the Start lag with an activity, and link them with FS to get around the problem, but I also want to give him the option of a settings solution, if one exists.
The project was created in MSP 2010, but I am using MSP 2003 to review it.
Thanks in advance,
G