Reported effort match
80%

The trailing average of builds whose reported effort size matched their estimate. This measures reported effort matches, not independently verified scope accuracy.

Cycles measured
398
Build reports
3,976
Sent back at review
4%

16-cycle trailing mean of reported effort matches, per cycle.

Estimate accuracyPlannedDelivered
80%

of builds land on the exact effort the plan called for. Planned points against delivered points, cycle by cycle.

Review pushback
4%

of reviewed work gets sent back for changes. That is 119 of 2,790 tasks across every cycle.

Where the numbers come from

Read live from PAPI’s own Supabase, scoped to this project alone: the planning snapshots it writes each cycle, every build report, and every review verdict. No other project’s data appears here. The figures refresh whenever this page is requested, so they move as PAPI keeps shipping.

  • Reported effort match is the 16-cycle trailing mean of builds whose estimated and reported actual effort sizes match. It does not use the scope grade. The separate scope grade is a builder self-assessment, not an independently verified measurement; review iterations do not establish whether scope was accurate.
  • Estimate accuracy is the share of build reports where the planned effort size matched the actual, on the XS to XL scale.
  • Review pushback is the share of reviewed tasks that took more than one pass or a non-accept verdict.

Plan your build the same way.