Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ASAP and ALAP options for tasks #280

Open
GoogleCodeExporter opened this issue Jun 28, 2015 · 8 comments
Open

ASAP and ALAP options for tasks #280

GoogleCodeExporter opened this issue Jun 28, 2015 · 8 comments

Comments

@GoogleCodeExporter
Copy link

Please add ASAP and ALAP options for tasks. 

Original issue reported on code.google.com by strakho...@gmail.com on 26 Aug 2011 at 2:15

@GoogleCodeExporter
Copy link
Author

Care to explain what do you mean? Tasks in GanttProject are scheduled in ASAP 
manner. ALAP doesn't make too much sense if there is no backward scheduling 
(and there is no such scheduling in GanttProject). 

Original comment by dbarashev on 3 Sep 2011 at 11:22

@GoogleCodeExporter
Copy link
Author

Thank you for your response.
ALAP is a valuable option. It is a default one for Critical Chain Project
Management.
Unfortunately there is none in GanttProject.

Original comment by strakho...@gmail.com on 4 Sep 2011 at 12:49

@GoogleCodeExporter
Copy link
Author

So is the request to support Critical Chain or just add one more field to tasks 
which could be just ignored by GP scheduling algorithms?

Original comment by dbarashev on 4 Sep 2011 at 11:10

@GoogleCodeExporter
Copy link
Author

Supporting ALAP would be good.
Support of Critical Chain (with buffer management) would be great if
possible.

Original comment by strakho...@gmail.com on 5 Sep 2011 at 2:51

@GoogleCodeExporter
Copy link
Author

If just "support ALAP" is good, in the sense I written above (just a field 
which means nothing to GanttProject scheduling algorithms) then could you use a 
custom field for that?

Original comment by dbarashev on 5 Sep 2011 at 9:28

@GoogleCodeExporter
Copy link
Author

Changing type to "discussion" as it is not clear what exactly is requested

Original comment by dbarashev on 9 Oct 2011 at 12:00

  • Added labels: Type-Discussion
  • Removed labels: Type-Enhancement

@GoogleCodeExporter
Copy link
Author

Please do implement ALAP and make the scheduler aware of that. I find it quite 
useful even for forward-planning in a few cases with just-in-time delivery:
Say task B is a successor of task A. It also depends on parts C to be 
delivered, so the delivery has to be kicked of just in time. With ALAP, that's 
easy: make B a successor of C, and set C to ALAP. Without ALAP, C will be 
scheduled much too early, possibly years before the parts are actually needed.
In principle, there's another way to achieve this by setting C to be a 
successor of B instead, and choosing Start-Finish (SF). Then _usually_ C is 
shifted such that it ends exactly when B starts. But in principle it can also 
end _after_ B started, SF allows for that. In that case, the parts are 
delivered too late.
Please excuse me If I'm getting something completely wrong here and it's all 
not how project planning should work in theory, but that's how I found it works 
for me in practice. Just not with ganttproject, since it's missing ALAP.

Original comment by steinlec...@gmail.com on 22 Jan 2014 at 5:39

@GoogleCodeExporter
Copy link
Author

#7: I think Start-Finish trick will work, at least in GanttProject. If lag is 
set to 0 and dependency is strong then our scheduler makes sure that C ends 
exactly when B starts.

Original comment by dbaras...@ganttproject.biz on 22 Jan 2014 at 5:49

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant