Microsoft Project - Using "As late as possible" instead of SF dependencies



  • Im new to project and im trying to link task 2 to a activity in task 1 so that all of the earlier activities in task 2 then work backwards. I have read that i should be using "as late as possible" rather than using the SF dependencies and then linking all the tasks in reverse. This makes sense as having to write SF on every line item is extremely time consuming. Unfortunately im having some issues trying to implement it.

    enter image description here

    Ive set "Sub Task 2d" to start as late as possible and SS with "Sub Task 1c". I understand that SS means task B cant start before Task A has started, and its taking "Sub Task 1e" as the last project date, so its finishing then.

    When i change this to SF, and keep "as late as possible" i though SF meant Task A must start before Task B can finish, so why hasnt Task B (Sub Task 2D) moved earlier so its finish time coincides with the start of Task A (Sub Task 1C) and Sub Task 2A-2C also then moved earlier due to Sub Task 2D moving??

    enter image description here

    Any help would be much appreciated.

    $$ Edit $$

    The following seems to work but im not sure if this is a bad practice. Sub Task 2d has predecessors set as 12sf,6sf and its set to ASAP. All other Sub Task 2 activities are set to ALAP.

    enter image description here



  • As noted in the comments, neither SF links nor ALAP constraints generally satisfy the need for scheduling just-in-time work. This figure shows a new readiness milestone linking to a new lead-time activity. (The lead-time activity is needed only for delaying multiple tasks together. For just-in-time shipment/delivery, only the milestone is needed.) Not perfect, but fairly robust and gets the job done without destroying logic flow. enter image description here



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2