Hi, Sugan

In the beginning, there was a lot of focus on the critical chain, and
it was good. In the fullness of time, most have realized it doesn't
mater that much. Its just a tool to get adequate time planned for all
resources to have a reasonable chance to get all their stuff done to
complete the project by the due date., and to help with synchronizing
the flow of work.

During execution, all you need to know is the buffer impact of the
tasks. Priority goes to the task with the greatest buffer penetration.
Buffer recovery starts with the task causing the greatest buffer
penetration.

In the beginning, critical chain tasks start with zero buffer
penetration, and feeding chain tasks start with negative buffer
penertation equal to the appropriate feeding buffer. Thus, in the
beginning, critical chain tasks get prioity. After that, the critical
chain per-se simply does not matter.

When a feeding chain generates the most buffer penetration, some choose
to call it the "longest chain". Some choose to call it the "new
critical chain". I don't call it anything, because to me, it does not
matter.

Regards,
Larry Leach




--- In CriticalChain@yahoogroups.com, "sugan685" <sugan685@...> wrote:
>
> Dear All,
>
> Does Critical chain must remain constant during the entire project ,
> if yes
> In case due to buffer penetration new resource conflicts are created
&
> therefore we need to recompute the critical chain .
>
> I am new to this field . Please guide me.
>
> Regards,
> Sugan
>