Projects by Periscope use special schedule techniques that let us see to the end of the project, so we know early in the project if we are a few days behind, while there is still considerable time to react. Otherwise, a team often learns near the end of the project that it is weeks late, with little chance of recovery, and lots of management angst.
There are many reasons that projects are always late. Understanding those reasons helps us improve your on-time performance.
One problem is with the way we estimate duration. We often insist on the most optimistic estimate of numerous sequential tasks. The result is a statistical certainty that the project will be late.
Another problem is with human behavior, something called the “student syndrome,” a form of procrastination. Frankly, many people don’t begin to work on a task until it is nearly due because they are busy with other things. In Project Management vernacular this means we work on a task "as late as possible" time before the next task is due to start, instead of the "as soon as possible" time we could have worked on our task. This scenario also virtually guarantees a late project.
The good news is that Periscope's schedule techniques integrate the scope and schedule so that no work goes unscheduled. We estimate duration with PERT estimates. And we manage contingency time like a contingency budget, creating behavior changes that can address these problems, resulting in realistic schedules and on-time performance.