Login

Welcome, Guest. Please login or register.

November 01, 2025, 10:16:09 am

Author Topic: crashing networks  (Read 1106 times)  Share 

0 Members and 1 Guest are viewing this topic.

lacoste

  • Victorian
  • Forum Leader
  • ****
  • Posts: 973
  • Respect: +2
crashing networks
« on: October 05, 2009, 04:16:58 pm »
0
If i reduce the length of an activity not on critical path will it not affect the early completion time?

in other words, is this statement true, if you reduce activities on critical path the time reduces, if reduce on non-critcial path the time will not be affected ALWAYS?

plato

  • Victorian
  • Forum Obsessive
  • ***
  • Posts: 317
  • Respect: +11
Re: crashing networks
« Reply #1 on: October 05, 2009, 11:12:27 pm »
0
If i reduce the length of an activity not on critical path will it not affect the early completion time?

in other words, is this statement true, if you reduce activities on critical path the time reduces, if reduce on non-critcial path the time will not be affected ALWAYS?

Reducing any activity that is not on the critical path will not affect the minimum time needed to complete the project. This time is determined by the critical path activities only. Beware that crashing an activity on a critical path could create a new critical path that will include one or more activites that were not previously critical but have become so - and so reducing these new activities now MAY impact on project completion time.

I stress this MAY impact - it will do so only if another (new or old) critical path of equal timing does not concurrently exist.

lacoste

  • Victorian
  • Forum Leader
  • ****
  • Posts: 973
  • Respect: +2
Re: crashing networks
« Reply #2 on: October 06, 2009, 04:20:37 pm »
0
so if a new critical path works, do we accept the new critical path or ignore it and try to make the old critical path equal the other.

plato

  • Victorian
  • Forum Obsessive
  • ***
  • Posts: 317
  • Respect: +11
Re: crashing networks
« Reply #3 on: October 06, 2009, 08:51:40 pm »
0