Commitment Accuracy

Summary

The Commitment Accuracy metrics in Allstacks help project managers and engineering leaders track how reliably milestones such as Epics and Initiatives are delivered in relation to their target end dates. It provides three metric views to measure delivery consistency over time.

The Different Views

1. By Deliverable, Target – This metric shows the overrun for each individual milestone that was completed late in the last 90 days. On the X axis appears the name of each milestone. It shows three series: 1. The number of days the milestone was over the original target end date when it was completed, the number of days the milestone was over the final target end date when it was completed, and the number of times the target end date was changed.

2. Trend, Target – This metric shows the overrun trend over time, showing the same series as the previous view, but grouped by week instead of by milestone. Milestones completed in the same week have their number of overrun days averaged together.

3. By Deliverable Histogram – This metric displays a count of completed milestones in histogram buckets according to how far past their target date they were at time of completion. Ideally, the first bucket is by far the largest, indicating items tend to get completed close to the original target.

Important Notes on How This Metric Works

• Only Items with a Due Date Are Tracked – If a deliverable does not have a due date set in Jira or ADO, it will not appear in this metric. The chart only includes items with defined target dates.

• Only Completed Items Are Included – The metric only counts items that have been closed within the selected reporting period. Items that remain open, even if they are past their due date, are not included. This ensures that the data reflects actual completion times rather than ongoing work that might still be in progress, or work that was abandoned long ago.

• Tracks Parent-Level Objects by Default – The chart primarily includes epics, initiatives, and features—larger deliverables that typically contain stories and tasks.

• Customizing Parent Objects – If your team uses custom milestone objects in Jira or ADO, Allstacks can be configured to recognize them as parent-level items. By default, only standard epics, initiatives, and features are tracked, but additional object types can be added based on your needs.

By tracking these metrics, teams can assess how predictable their delivery timelines are and make data-driven adjustments to improve planning and execution.