This topic contains 3 replies, has 2 voices, and was last updated by Carlos Santos 2 months, 2 weeks ago.
- 11/26/2018 at 5:51 pm #414146
“In MS Project 2016 how can one tell which of the tasks that appear on critical path are not all critical, in other words how can I tell which ones are not critical since they all have total slack = 0 days,I know for sure some are not critical but is there way other than testing with changing duration, manually ? I need to know this please help because spending hours testing one by one:11/27/2018 at 9:38 am #414152
Williams, unfortunately they are all critical in the eyes of the Project formula. There are considerations based on rules. Constraints and deadlines affect critical path, maybe others I can’t remember but there are plenty of articles and videos that provide details. Hope that helps…11/27/2018 at 11:38 am #414153
1. MS Project defines “Critical” tasks as those incomplete tasks with Total Slack <= 0. (You can increase but not decrease this threshold in the advanced options.) The collection of “Critical” tasks represents the true Critical (logic) Path under some very limited conditions; e.g. only one calendar, no constraints, no deadlines, no resource-leveling, no out-of-sequence progress.
2. Assuming you’ve met other requirements of good scheduling practice (e.g. no “manually-scheduled” tasks, no inactive tasks, no logic on summaries, no logic open ends), then you should be able to define the Critical Path as the driving logic path to the project completion milestone. In MSP 2016 you can identify this path using the Task Path bar styles for “DrivingPredecessors.” It works fairly well for simple projects but is unreliable in the presence of logic that is not Finish-to-Start. It also fails in the presence of out-of-sequence progress and does not penetrate cross-project links (in linked master/sub-projects). If you need, here’s a Macro for Filtering based on “Task Path” in Microsoft Project: https://wp.me/p6CCB4-km.11/28/2018 at 10:57 am #414157
Please read this article.