Joe P. is currently managing a project that's behind schedule and he's experiencing substantial pressure to get the project back on track.
Joe is responsible for managing a project for which the [Expected Completion Date] is later than the [Deadline]. This situation creates a [Schedule Gap] and Joe is getting rather intense pressure to get the project back on track. So what action should he take?
The immediate action may be to employ [Overtime] to essentially increase the labor quantity thus reducing the [Expected Completion Date]. This should create Overtime Imp Balancing Loop (B1) and help get the project back on track. Though do you think it's really this easy?
If [Overtime] continues for any lengthy period it is likely to result in [Fatigue]. [Fatigue] tends to reduce [Labor Productivity] thus moving out the [Expected Completion Date]. Here we have the Fatigue Delay Reinforcing Loop (R2) taking us in a direction that we definitely don't want to go.
As such, [Overtime] may be a viable option, as long as it's not likely to last very long. In this particular case the [Expected Completion Date] is so far off from the [Deadline] it is expected that [Overtime] would have to be employed from now till the end of the project, which is projected to be several months. [Overtime] isn't looking like a viable option here. So now what?
An alternative might be to add [Resources] to increase the [Labor Quantity]. This should then move in the [Expected Completion Date], or would it?
The risk associated with adding new [Resources] is that they have to be brought up to speed, which can actually diminish the [Labor Productivity] for a period of time. As such it's appropriate to determine if the longer term benefits outweigh the shorter term negative aspects.
So what's the real answer? For another perspective please join us in the "Credit Never Happened" model.