'Missed tasks' quality metric
Use this metric to check the proportion of tasks in the live data that have a finish date later than the finish date of the corresponding task in the current baseline. A high proportion of "missed" tasks can indicate that a schedule is not proceeding according to plan.
With the pass and fail boundaries set to 5.00%, this metric meets the requirements of DCMA test 11 (Missed tasks).
Example of "missed tasks"
In the following illustration, the baseline tasks are shown immediately beneath the corresponding tasks in the live data. The finish date of Task 1 in the live data is identical to that of the corresponding task in the current baseline and the finish date of Task 3 in the live data is earlier than that of the corresponding baseline task. These two tasks would pass this metric. The finish dates of tasks 2 and 4 in the live data are later than the finish dates of the corresponding baseline tasks. These two tasks would fail this metric:
You can change the impact that this metric has on the weighted total result of a quality check by entering a factor by which the quality metric should be multiplied in the Weighting field. For the weighting to have any effect, a quality check must have more than one quality metric.
Pass and fail criteria
| Pass or fail? | Criteria |
|---|---|
| Pass |
A project passes this metric if the percentage of tasks in the live data that have a finish date later than their finish date in the current baseline is less than or equal to the pass boundary percentage.
For example, if the pass boundary was set to 5.00%, a project would pass this metric if 5.00% or less of tasks in the live data had a finish date later than the finish date of the corresponding task in the current baseline. |
| Fail |
A project fails this metric if the percentage of tasks in the live data that have a finish date later than their finish date in the current baseline is greater than the fail boundary percentage.
For example, if the fail boundary was set to 5.00%, a project would fail this metric if more than 5.00% of tasks in the live data had a finish date later than the finish date of the corresponding task in the current baseline. |
| Neither pass nor fail | If the percentage of tasks in the live data that have a finish date later than their finish date in the current baseline falls between the pass and fail boundary, the result is neither a pass nor a fail, but somewhere in between. |
Suggested settings to meet the requirements of DCMA test 11 (Missed tasks)
- Pass boundary: 5.00%. A project will pass this metric if 5.00% or less of tasks in the live data have a finish date later than the finish date of the corresponding task in the current baseline.
- Fail boundary: 5.00%. A project will fail this metric if more than 5.00% of tasks in the live data have a finish date later than the finish date of the corresponding task in the current baseline.
Does the metric force a project to be rescheduled?
No.
Suggested actions if a project fails this metric
If a project fails this metric, select the metric in the Quality Check Results dialog and click Show Failing Tasks to view the tasks that have failed the metric.
You could take the following actions to remedy the failing tasks:
- Review the tasks in the live data to determine whether there is any way of shortening the project.
- Review the current baseline to determine whether the planned schedule is realistic.