2 ms·
The uncertainty doesn't have to result in people standing around though; that should [0] manifest as periods where the job site is empty because there is a shor
by roenxi 4y ago
The uncertainty doesn't have to result in people standing around though; that should [0] manifest as periods where the job site is empty because there is a short period of slack in the schedule.
And it is easy to over-sell the variance of tasks. These things have regular and predictable times with rare outliers. The challenge of scheduling them is nothing like the impossibility of scheduling a software project accurately.
[0] Lots of exceptions, yes. No I don't know anything about construction but I do know quite a bit about scheduling work.
- Retric 4y agoThe differences in construction are relevant here. Construction work involves people and machinery which can’t easily move between locations the way programmers can hop between tasks. Further there are orders of magnitude cost differences between people and machinery. The guy with a shovel standing next to heavy machinery might not actually do much labor in a given hour, but sending them elsewhere would be a mistake.
- roenxi 4y agoPrecisely. You're describing a scenario where the variance of the task time has little to do with why people are standing around. The tasks could have 0 variance and there would still be people standing around. Probably for the same amount of time, in practice. The situation is controlled by the cost of moving equipment around & the order tasks need to be done. The uncertainty would manifest as periods of buffer when equipment isn't bought to site yet/men don't get bought in at all. Obviously sometimes the situation just falls apart, but usually I'd bet the downtime would be planned and predicted.