Schedule Overrun occurs when a project’s time restriction is violated. In other words project doesn’t meet its expected deadline as some of tasks from its Critical Path have been delayed by the project team. Schedule Overrun makes the Project Customer not satisfied by performance of the team, as the project has run out of its predefined timeframes, but the desired products haven’t been delivered to the Customer yet. Schedule overrun may mean not only non-meeting of the final due date of a project, but also missing to match predefined project milestones while this project is still in process, which may underlie further delay if not rectified as appropriate.
The main reasons for Schedule Overrun can be the following:
- Poorly performed time estimation of the project tasks and activities (in other words the project schedule was not fully accurate and feasible);
- Risks were underestimated on the project planning phase (some of project risks occurred much more threatening than thought before);
- Unforeseen circumstances and factors hampered the progress (something really unpredictable has broken the project plans, let’s say a tornado);
- Poor quality control caused frequent and costly reworks (the quality management system wasn’t properly implemented and it wasn’t able to fulfill its functions on every step);
- Poor work organization and planning;
- Internal conflicts within the project team;