In general, constraining the estimated time to completion can telegraph redundancy is necessitated in a complex project. https://en.wikipedia.org/wiki/Program_e

In general, constraining the estimated time to completion can telegraph redundancy is necessitated in a complex project. https://en.wikipedia.org/wiki/Program_evaluation_and_review_technique https://en.wikipedia.org/wiki/Program_evaluation_and_review_... Or from another perspective, the probability a given team can successfully finish a key project deliverable diminishes after a projected time. If the hard parts of a problem still remain, the progress has in fact stopped when resources start being diverted to non-critical tasks. The statistics indicate if a person says they are 95% certain, they are in fact 60% certain, and unaware of their bias. Good luck convincing the Dev-ops crowd though... being busy means progress to some folks. ;)