Estimates of task complexity that are inaccurate.
Unidentified dependencies in your schedule.
The risk that an important dependency will not be met resulting in broad delays.
Cost overruns and other budget issues.
Risks related to employees such as absenteeism or employee turnover.
The risk that technology with be disrupted, unavailable or unfit for purpose.
The risk of infrastructure outages such as a closed road.
Risks related to a facility such as a shutdown that impacts access to an office.
Failures or low performance of a partner.
The risk of low team performance.
The potential for low quality deliverables that require rework.
An invalid structural design.
Problems with designs and a need to restart things at the design level.
A tendency for scope to increase due to factors such as undocumented assumptions.
The risk that disputes will delay a project.
Unexpected poor or severe weather.
The risk of major adverse events beyond your control such as a fire.
The potential for a cybersecurity incident to derail or delay a project.
The risk of delayed regulatory approvals such as permits.
|Overview: Schedule Risk|
The potential for a strategy, project or task to take longer than scheduled.
A developer estimates a task duration of 5 days but takes 15 days to deliver due to unanticipated technical hurdles. A schedule assumes that data center facility will be available for the testing phase of a project. However, a security incident delays access to the facility.A previously unidentified dependency prevents a task from beginning as scheduled until a long running task is completed.