A project is one bounded piece of work with an end. Coordinating several toward a shared outcome is\npmo:program-management.
Inclusions are agreed easily and understood differently. The exclusions do the work: what this\nproject will not deliver, written down and acknowledged by the sponsor.
\nUnwritten exclusions return as assumptions, always late, always framed as something obviously\nincluded. Fixing that at the end is called scope creep; it is usually a documentation failure at the\nstart.
\nA single-point estimate is a forecast presented as a commitment. Give a range with the assumptions\nthat would move it, and be explicit about confidence.
\nEstimate the work, not the desired date. Estimates negotiated downward do not change the work; they\nchange when you find out, and the finding-out happens at the least recoverable moment.
\nDecompose until the pieces are comprehensible. Estimating a large unknown produces a number\ncorrelated with optimism rather than with the work.
\nNot everything late matters. Slippage on the critical path moves the end date; slippage elsewhere\nconsumes float. Knowing which is which is the difference between useful concern and generalised\nanxiety.
\nRecalculate as things change — the critical path moves, and a team watching the original one is\nwatching the wrong thing.
\nHold buffer at the project level rather than padding each task. Padded tasks absorb their own buffer\nand deliver no earlier, because work expands and nobody reports finishing early.
\nPercentage complete is self-reported optimism, and it famously stalls at 90%. Track binary completion\nof defined deliverables — done or not done, judged against a definition agreed in advance.
\nWatch the trend: whether the amount remaining is falling at the rate required. A project where\nremaining work is not decreasing is a project that is late, whatever the reported percentage.
\nDiagnose first, since remedies do not overlap: scope larger than understood, capacity lower than\nplanned, dependencies not delivering, or an estimate that was never realistic.
\nThen present options with consequences — cut scope and name what, extend and say by how much, or add\ncapacity, which late in a project usually slows things further. Re-baseline once, visibly. Serial\none-week slips destroy credibility far faster than a single honest reset.
\n