Schedule check and quality
The points of attention found and the DCMA quality score.
In the Schedule check block, UProject lists the problems found, with severity (error, warning or information) and a link to go to the task.
- File not recalculated before exporting, tasks without dates, finish before start and circular dependency.
- Summary with dates different from its tasks, negative slack and missed deadline.
- Hard constraints, tasks without a predecessor and tasks without a successor.
Quality score (DCMA)
The score from 0 to 100 uses the schedule quality criteria adopted by PMOs (DCMA 14-point): logic, leads, lags on links, link types, hard constraints, slack, long tasks, invalid dates, tasks without resources, tasks late against the baseline, the baseline execution index (BEI), the critical path test and the CPLI. Hover over each criterion to see what it measures.
- Critical path test: UProject simulates a 600-day delay on the first open critical task (on a copy, without changing the schedule) and checks whether the project finish slips by the same amount. If it does not, the critical path is broken: a link is missing.
- CPLI: (time to the forecast finish + slack to the required finish) ÷ time to the forecast finish. The required finish is the deadline on the project row or, without it, the baseline finish. Below 0.95, the project will not meet its deadline.
Tip: Schedules with more than 400 tasks go without these two tests, because the simulation takes long.