Skip to content

Set realistic due dates from velocity

Use this when: You are asked for dates without having a basis for them, or work repeatedly finishes late.

You need:

  • Sizes on tasks; see Estimates and velocity
  • Completed work consistently marked complete
  • Several weeks of data; one or two weeks can vary too much

Open Insights → Velocity and review completed size over recent weeks.

Use a lower recent value as a conservative starting point. An average can leave too little room for slower weeks.

Filter to the relevant project and total the sizes of incomplete tasks.

Estimated weeks ≈ Remaining total size / Weekly velocity

This estimates the time needed at the pace you have sustained.

Account for differences between the historical pace and the planned work:

  • Shared availability: Divide by the fraction of capacity available to this project, if your baseline assumes full availability.
  • Holidays and leave: Exclude those days from the working calendar.
  • Waiting for review: Check actual waiting time in Risks and allow for it where it is not already reflected in the baseline.

Avoid counting the same constraint twice. Long review waits can dominate the schedule: reducing coordination delays may matter more than speeding up execution.

For example: “We have 80 points remaining. At 18 points per week and 70% availability, that is about 6.3 weeks. Adding two days for review gives us roughly seven weeks.”

This makes the assumptions open to discussion, instead of relying on “probably by the end of the month.”

Find out where the extra time went:

  • Slower execution shows up in velocity.
  • Longer waits show up in Risks.

If waiting is the cause, adding more people to execution may not help. See Reduce time waiting for review.