Dependencies dictate the type of preceding activity that must occur prior to a succeeding downstream SmartTask being started or completed. Note that in Moovila once a SmartTask has been cancelled it will no longer be factored into the Critical Path. Four types of dependencies exist:

  • Finish-to-Start: The preceding SmartTask must be completed before the next SmartTask can begin. This is the most common type of dependency.
    mceclip0.png
  • Start-to-Start: The preceding SmartTask must start before the next SmartTask can begin.
    mceclip1.png
  • Finish-to Finish: The preceding SmartTask must be completed before the next SmartTask can be completed.
    mceclip2.png
  • Start-to-Finish: The preceding SmartTask must start before the next SmartTask can be completed. This is the least common type of dependency
    mceclip4.png

“Lag” and “Lead” can be introduced to dependency types to alter the execution time between dependent SmartTasks.

  • Lag: The amount of time that is added between a preceding SmartTask and the next SmartTask. For example, a two day lag would mean that the next SmartTask begins two days after completion of the preceding SmartTask.
  • Lead: The amount of time the next SmartTask is accelerated based on its preceding SmartTask. For Example, a two day lead would mean that the next SmartTask begins two days before the completion of the preceding SmartTask.

Use the Dependency Editor to Specify Dependency Type, Lag, and Lead.

  1. Open the project in the Critical Path Engine view, then click the Edit icon.
    mceclip0.png
  2. A purple dot appears on dependency lines, indicating they are now editable.
    mceclip1.png
  3. Click a purple dot. The Dependency Editor screen appears.
    mceclip6.png
  4. Select the Dependency Type by clicking one of the options. For this example, Finish-to-Start (meaning that we must complete the Schedule Process Documentation Meeting SmartTask before the Post Meeting Findings Processing SmartTask can start).
  5. Select a Lag or Lead. In this example, a 1-day lag has been set.
    a.  Click Lag and not set. The Lag Lead Amount screen appears. 
    mceclip8.png
    b. Use the number pad and unit of measure options to select the lag or lead time. Click OK. The Dependency Editor screen appears with the selections visible.
    mceclip9.png
    c. Click the Back arrow to return to the Critical Path Engine. The path now displays changes to dependencies with the lag or lead applied.
    mceclip2.png

    In this example:

    • System Testing will be completed 11/18 and User Training can’t start until that happens.
    • With the addition of a two day Lag, the SmartTask that should have started on 11/19 now gets started on 11/21 instead. The change in those dates is reflected above the SmartTask, with the original dates appearing in black and the proposed new dates appearing in purple.
    • The SmartTask will now conclude on November 22nd.
    d. Zooming out, the dates for the next SmartTask on the Critical Path are impacted as well. This is apparent in the dates that appear above the SmartTask tile.
    mceclip3.png
    e. To save these changes, click the Save button in the upper right of the screen. The Update Timeline window opens.
    mceclip4.png
    f. Toggle Settings to:
    • Update Tasks with Proposed Dates: This will make the purple dates that Moovila has provided above the original red dates the official dates for those SmartTasks. The timeline will update accordingly. NOTE: Ensure that all changes are approved before updating task with proposed dates, as these updates are final and cannot be reverted.
    • Send Change Notifications: If the SmartTasks are updated with the proposed dates, it will be possible to notify members of the team of the changes via this setting.
    g. Click Save to continue. If the SmartTasks’ dates have been updated, they will be reflected in the Critical Path after saving.
    mceclip5.png
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.