none
Critical Activities RRS feed

  • Question

  • MSP reflecting list of activities as critical while expediting / delaying few of them it is not impacting project overall finish date. Any suggestions / errors for resolving.
    Tuesday, November 19, 2019 7:11 AM

All replies

  • You don't give us much to go on

    Do you mean that the critical tasks are red bars on the chart?

    In the schedule table, do they have zero total slack?

    Can you run the filter for critical tasks?

    Can you group on critical?

    Are they all auto scheduled?

    How are you tracking progress?

    Do they have different calendars?

    Are there any date constraints?

    Any resource leveling been done?

    What do you mean by "expediting / delaying few of them"?

    Does every task have at least one FS0 predecessor and at least one FS0 successor>

    Do any summaries have predecessors or successors?

    Tuesday, November 19, 2019 1:01 PM
  • Do you mean that the critical tasks are red bars on the chart? - Yes

    In the schedule table, do they have zero total slack? - Yes

    Can you run the filter for critical tasks? - Done

    Can you group on critical? - Done

    Are they all auto scheduled? - Yes

    How are you tracking progress? - Via custom reports & Tracking Gantt

    Do they have different calendars? - No

    Are there any date constraints? - Yes, 

    Any resource leveling been done? - No

    What do you mean by "expediting / delaying few of them"? - while the "actual finish" or "finish" is delayed for few of them

    Does every task have at least one FS0 predecessor and at least one FS0 successor> - No

    Do any summaries have predecessors or successors? Yes

    Tuesday, November 19, 2019 1:08 PM
  • Well, then, if there are tasks which do not have predecessors or successors, and if there are summaries which do have predecessors/successors (well known to be a poor scheduling practice), I would say that your problem is right there. Difficult to say without seeing it. Can you provide a screenshot, or make the file available?

    Do any tasks have predecessors with negative lag (well known to be a poor scheduling practice)?

    Are all of the actual starts, actual duration and actual finishes on the left of the status date (ie in the past relative to the status date) and all of the scheduled/planned start, duration and finish on the right of the status date?

    Wednesday, November 20, 2019 3:29 AM
  • Few tasks do not have successors as they are the last tasks in the queue followed by the last task. one of the reason for not linking it with the last task was there may could be too many such tasks getting reflected as the predecessors of the last tasks. Linking summary tasks leads in resourcing issues, resource productivity is not getting tracked in the said project, is there any other implication.

    Are all of the actual starts, actual duration and actual finishes on the left of the status date (ie in the past relative to the status date) and all of the scheduled/planned start, duration and finish on the right of the status date? Yes

    Wednesday, November 20, 2019 5:45 PM
  • Have to see it. Screenshot? Just guessing otherwise.

    You must remove predecessors/successors from summaries. MSP allows it. Don't do it. Otherwise, it is impossible to find a critical path.

    You must provide at least one FS0 successor for every task. If nothing else then it must be the project finish milestone.

    In file, options, advanced (or maybe in schedule) MSP calculates multiple critical paths?

    What does the schedule table look like?

    Thursday, November 21, 2019 10:27 AM
  • I agree summary tasks ideally should not be linked while it can lead to issues like reflection of resource over-utilization etc.

    While it is specifically done considering resource utilization is not tracked therein & eliminating multiple linkages required

    In this scenario like this does it mean that if summary tasks are critical & linked then in that case all of tasks below will become and reflect as critical

    Thursday, November 21, 2019 12:29 PM