See what's new on Keypup!  📢

Overdue Pull Requests and Issues

Template providing the total number of items (including Pull Requests and Issues) still open after due date.

Get started with this Dashboard

Prioritize Your Overdue Pull Requests and Issues

with

Overdue Pull Requests and Issues

Detect planning, workload, or capacity issues with the overdue items metrics template.

Use Overdue Items Metric
Overdue Pull Requests and IssuesOverdue Pull Requests and IssuesOverdue Pull Requests and Issues

Understand the Overdue Items Metric Template

The overdue items metric template provides a count of pull requests and issues still open after their due dates.

How to Use the Overdue Items Metric Template

This KPI should be combined with the unaddressed overdue pull requests insights to drill down to details. In a nutshell, if: 

  • KPI shows 0: All items are currently on time. The output of your delivery may be increased if your KPI consistently shows zero. 
  • KPI occasionally shows between 0 and 5: A few items are late. Consider whether there is a systemic problem (e.g., review bottleneck), a seasonal problem (e.g., large projects or seasonal team shortages), or an isolated problem (e.g., implementation complexity underestimated).
  • KPI consistently shows 5+ items: Deliveries are systematically late. It could be the result of a large backlog of work being cleared (for instance, the team is catching up after a large release). The team may benefit from some time to regroup and process outstanding tasks.
  • KPI shows 5+ items and is rising over time: The delivery team is not following the pace of development set by the product or leadership team. Current development capacity is probably not able to meet the objectives. Priorities need to be revisited.

How to Improve the Overdue Items Metric

  • You can begin with a small delivery throughput and increase it over time. 
  • You should limit how many items (or story points) you schedule at a time.
  • Make sure issues are relatively consistent in size. As a result, it is easier to monitor the scheduled backlog.
  • Make sure you have an adequate prioritization process and an owner (e.g., team lead, project manager, product manager, VP of engineering, CTO).
Use Overdue Items Metric

Understand the Overdue Items Metric Template

The overdue items metric template provides a count of pull requests and issues still open after their due dates.

How to Use the Overdue Items Metric Template

This KPI should be combined with the unaddressed overdue pull requests insights to drill down to details. In a nutshell, if: 

  • KPI shows 0: All items are currently on time. The output of your delivery may be increased if your KPI consistently shows zero. 
  • KPI occasionally shows between 0 and 5: A few items are late. Consider whether there is a systemic problem (e.g., review bottleneck), a seasonal problem (e.g., large projects or seasonal team shortages), or an isolated problem (e.g., implementation complexity underestimated).
  • KPI consistently shows 5+ items: Deliveries are systematically late. It could be the result of a large backlog of work being cleared (for instance, the team is catching up after a large release). The team may benefit from some time to regroup and process outstanding tasks.
  • KPI shows 5+ items and is rising over time: The delivery team is not following the pace of development set by the product or leadership team. Current development capacity is probably not able to meet the objectives. Priorities need to be revisited.

How to Improve the Overdue Items Metric

  • You can begin with a small delivery throughput and increase it over time. 
  • You should limit how many items (or story points) you schedule at a time.
  • Make sure issues are relatively consistent in size. As a result, it is easier to monitor the scheduled backlog.
  • Make sure you have an adequate prioritization process and an owner (e.g., team lead, project manager, product manager, VP of engineering, CTO).
Use Overdue Items Metric