Deploy free

Delivery trend: the calendar is doing half the explaining before you even open your mouth

The delivery trend is a weekly count of items shipped from Jira and Azure DevOps, plotted as a line — with two things stacked on top of it that most throughput charts skip. Shaded bands mark calendar events (freezes, migrations, holidays), and the single best week gets an automatic peak marker. The point is simple: don't investigate a dip the calendar already explains.

deckgauge · Board · Intelligence
Shaded band = calendar eventPeak week

Ten weeks delivered, with one shaded freeze band and the auto-marked peak.

What it measures, and where the data comes from

The line itself is unremarkable on purpose: a count of items delivered per week from Jira and Azure DevOps, same underlying data as any other throughput view. What makes this one different is the annotation layer sitting on top of it.

  • Shaded bands — calendar events marked against the board: code freezes, infra migrations, company or regional holidays. An event can be scoped to one board or set company-wide, so a shared holiday shows up shaded across every team's chart without anyone re-entering it per board.
  • Peak marker — the single highest-delivered week in the window gets flagged automatically. No judgment call, no manual pin — just whichever week counted the most.
Bands explain, they don't excuse everythingA shaded band means a known event happened that week — it doesn't automatically mean that event caused the dip. Most of the time it did. Don't let the band become a reflexive alibi for a team that's genuinely slowing down for other reasons too.

How to read it

Check every dip against the bands before you react to it. A dip sitting inside a shaded region is the calendar doing its job — a freeze week, a migration cutover, a holiday nobody was going to ship through anyway. That's not a team problem, and treating it like one just teaches people to pad their estimates around freeze weeks forever.

A dip with no shaded band anywhere near it is a different animal entirely. Nothing on the calendar explains it, which means something in the work itself does — and that's worth ten minutes of actual digging instead of a shrug.

What it tells you over time

Where the peak marker lands relative to the bands is its own small story. A peak sitting right after a freeze band is normal — pent-up work releasing all at once. A peak with no band nearby at all is more interesting: something the team did that week worked, and it's worth finding out what before it's forgotten.

Example situations

1. A dip that the calendar already explains

deckgauge · Delivery Trend

The low week sits squarely inside the shaded freeze band.

What you're seeing: weeks 6 and 7 are the low point of the whole ten-week window, and both fall inside the shaded band — a year-end code freeze the board already has marked. The line recovers immediately once the band ends.

How to react: don't investigate this. That's the whole point of the band being there. If leadership asks why delivery dropped that fortnight, the answer is one sentence and it's already on the chart — no retro needed, no root-cause exercise, no team defensiveness about a slow week that was never supposed to be a fast one.

Managerial playPoint at the band, say the sentence, move on: "that's the freeze, it's expected." Save your actual attention for dips that don't have an explanation sitting right there — spending a retro item on a freeze-week dip trains the team to expect scrutiny for things that were never a problem, which is a worse habit to build than the dip itself.

2. A dip with nothing on the calendar to explain it

deckgauge · Delivery Trend

Week 5 drops hard — no shaded band anywhere near it.

What you're seeing: the same shape of dip as the first example, sitting alone in an otherwise unremarkable stretch — but this time there's no band under it. Nothing on the calendar this widget knows about happened that week.

How to react: this one's worth ten minutes. No band means the explanation lives somewhere else — an incident that ate the week, a key person out sick without it being logged as an event, a dependency that blocked several people at once, or simply a heavier-than-usual batch of hard tickets landing together. Check Work in Progress and Bug Rate for the same week before assuming it's a one-off.

Managerial playAsk the team directly what happened that week rather than guessing from the chart alone — a five-minute Slack thread usually surfaces it faster than cross-referencing three other widgets. If the cause turns out to be a real, recurring event type (an on-call rotation, a recurring dependency freeze) that isn't on the calendar yet, add it as a board or company-wide event now, so next time it shows up shaded instead of unexplained.

Frequently asked

What is the delivery trend widget?
A weekly count of items shipped from Jira and Azure DevOps plotted as a line, with shaded bands marking calendar events such as freezes, migrations and holidays, and an automatic marker on the single best week.
Why does it overlay calendar bands?
So you do not investigate a dip the calendar already explains. A drop that lines up exactly with a code freeze or a holiday week is not a delivery problem, and the overlay makes that obvious at a glance.
How do I tell a real dip from an explained one?
Check whether the dip sits inside a shaded band. If it does, the calendar accounts for it. If it falls in an ordinary week, it is worth asking about.

Related widgets

Last updated