![]() |
#1
|
|||
|
|||
![]() Hi I am using Project 2016 and met a client yesterday and found a difference in the way Project calculates Total slack. My client has the latest update and I do not. The difference is when I use Manually Scheduled Summary tasks. In my version Project checks the Finish date of the Manually Scheduled Summary task as a time set task so if the subtasks has a total duration of 8 Days and the Summary task a duration of ten Days the total slack is 2 Days. In my clients version the finish date of the Manually Scheduled Summary does not effect the total slack calculation at all. But the way I see it, this new calcualtion is wrong. Because if I have a deliverable and the Summary task is set to this date I want my total slack to use this date so I can use the critical tasks correct. I dont like this change but I dont Think I can persuade Microsoft to change it. So what do you Think is the best way to adapt to this new change? Hugo |
Tags |
critical task, total slack |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Uniform units for Total Slack | Crackers183 | Project | 2 | 05-07-2017 04:08 PM |
Total Slack Calculation Incorrect in SubProjects vs MasterPlan | ana | Project | 3 | 05-31-2016 07:58 AM |
Total Slack and Activity with SS Successor only | ketanco | Project | 3 | 05-14-2014 01:59 PM |
total slack of activities and schedule logic | ketanco | Project | 1 | 08-04-2012 05:58 AM |
Total Slack not updating | damianb | Project | 0 | 06-25-2010 11:48 AM |