Skip to content
ProductDevelopment.io
Insights & forecasts

Delivery dates from history, not from hope

12 report sections rebuilt from what actually happened to every ticket — and a Monte Carlo forecast that turns your own pace into a date range with odds.

Rebuilt from history

Charts that remember what really happened

Reports replay each ticket's recorded history in order. A ticket that moved to another project, was reopened, canceled or deleted still counts where and when it really was — and a finished cycle's scope stays as it was.

  • Rolling window of 1 to 90 days
  • Filter by project and cycle
  • Daily flow per stage category and per custom stage
DoneIn reviewIn progressTodo
Monte Carlo forecast

When will it be done? A range, with odds.

The forecast resamples your past weeks of completions 2,000 times to project when the remaining tickets will finish: P50, P85 and P95 dates, plus the chance of making a deadline. Runs are seeded, so the same history gives the same answer.

  • Needs at least 4 complete weeks and 10 completions
  • Says so instead of guessing when history is thin
  • Looks at most 365 days ahead
P50Oct 8
P85Oct 14
P95Oct 21

12 open tickets in scope. 2,000 simulations resample your past weeks of completions — and give the chance of hitting your deadline.

Lead & cycle time

Where time actually goes

Lead and cycle time with median, 85th percentile and mean, distribution buckets and the longest items. Time in stage and current stage waits show which step is the slow one.

  • Aging work and blocked work
  • Points by cycle and cycle scope
  • Delivery events: what finished, when
Median cycle time3.2 days
85th percentile7.5 days
Longest in reviewPD-388 · 9 days
Workload

Pace and capacity side by side

The overview puts created against completed over the last 7 days next to lead time, overdue work and each person's workload — so a forecast and a capacity problem are visible on the same screen.

  • Saved reports shared with the workspace
  • Settings are saved, results are always current
  • Agents run the same reports via MCP
Team & capacitypoints this cycle
AMA. MarchettiAvailable · 11/13
RNR. NakamuraBusy · 14/10
KOK. OseiAvailable · 6/12
SVS. VanceAway · 0/0
Insights & forecasts

Delivery dates from history, not from hope

Reports are rebuilt from each ticket's recorded history, so work that moved between projects, was reopened or was deleted still counts where and when it really was. Ask “when will this be done?” and get a range with a probability — in the app, or from your agent.

Cumulative flow · last 14 days

See where work piles up

Daily counts per stage category, and per custom stage, over a rolling window of 1 to 90 days. Filter by project or cycle.

DoneIn reviewIn progressTodo
Monte Carlo forecast

A date range, with odds

P50Oct 8
P85Oct 14
P95Oct 21

12 open tickets in scope. 2,000 simulations resample your past weeks of completions — and give the chance of hitting your deadline.

Lead & cycle time
Median cycle time3.2 days
85th percentile7.5 days
Longest in reviewPD-388 · 9 days
12 sections in every saved reportForecasts need at least 4 complete weeks and 10 completions — below that, the report says so instead of guessing.
Summary
Delivery events
Cumulative flow
Workflow stage flow
Lead & cycle times
Delivery forecast
Time in stage
Cycle scope
Current status
Points by cycle
Aging work
Blocked work

Give your next deadline a probability

Request access. Once you have a few weeks of history, the forecast has something to work with.