Support dependency offsets
As a project planner I need to be able to define a dependency with an offset.
Example: Task 5 can start 3 days after Task 4 starts. I would define that as a Start-to-start dependency from Task 5 on Task 4 with a +3 day offset.
Michael Kuhl
shared this idea
Hello!
Starting from version 2.2 Structure.Gantt has dependency lag/lead time support!
More details here: https://wiki.almworks.com/x/bQHdB
-
Will
commented
This would need to be done per task.
An example might be a backend build might be scheduled for an effort of 3 week, but a report build might typically be able to start 1 week prior to the backend build completion.
Therefor the offset would be something like "Is preceded by / offset - 5d". Alternatively a risk contingency might be built into some planning activities whereby the follow on task would have a "offset +2 d".
There are many many scenarios where this would be very useful, particularly when we use portfolio for JIRA and look to explore resource leveling. -
Admin[Deleted User]
(Admin, ALM Works)
commented
Thanks Michael!
-
Michael Kuhl
commented
Hi Alexey - This would be per dependency.
The offset implements a lag or lead time to the dependency (https://pmstudycircle.com/2013/02/lead-time-and-lag-time-in-project-scheduling-network-diagram/). So, for every dependency an issue has the offset as a lag or lead could be set (it would default to 0). If it's a lag it would a positive integer. A lead would be a negative integer.
Essentially it's an additional property of the dependency that drives the start date of the dependent task.