Critical Chain theory is to position tasks As Late As Possible (ALAP) when planning the project. Why does cc-Pulse position tasks As Soon As Possible (ASAP)?
The default setting for cc-Pulse is to position tasks as soon as possible (ASAP). cc-Pulse 2.2.0.7 (Released 10/30/2006) provides the option to position tasks As late As Possible (ALAP) in planning mode.
Starting ALAP in a multi-project environment does not allow sufficient slack in the feeding chains, since the feeding buffers are sized based on the single project paradigm, and there are often cross-project conflicts for resources.
On the other hand, starting ASAP in a multi-project environment enables any non-contiguous drum tasks in a single project to span a greater duration in some cases. In these cases, it is advantageous to plan the project in ALAP, and when the project is placed in tracking mode, to remove the Start No Earlier Than constraints on non-drum tasks, and re-level the resources. This provides the advantage of a compact drum schedule, and reduced risk for the non-drum feeding chains.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Critical Chain theory is to position tasks As Late As Possible (ALAP) when planning the project. Why does cc-Pulse position tasks As Soon As Possible (ASAP)?
The default setting for cc-Pulse is to position tasks as soon as possible (ASAP). cc-Pulse 2.2.0.7 (Released 10/30/2006) provides the option to position tasks As late As Possible (ALAP) in planning mode.
Starting ALAP in a multi-project environment does not allow sufficient slack in the feeding chains, since the feeding buffers are sized based on the single project paradigm, and there are often cross-project conflicts for resources.
On the other hand, starting ASAP in a multi-project environment enables any non-contiguous drum tasks in a single project to span a greater duration in some cases. In these cases, it is advantageous to plan the project in ALAP, and when the project is placed in tracking mode, to remove the Start No Earlier Than constraints on non-drum tasks, and re-level the resources. This provides the advantage of a compact drum schedule, and reduced risk for the non-drum feeding chains.