Sprint Reviews - Project Pulse
The whole delivery arc at a glance - health trajectory, throughput, carry-over debt, and per-cycle drill-down. Latest review: WK24 (health 77, delivery-first scorecard). Every number below comes from one source (registry/delivery.authored.ts).
Health Trajectory
Cycle health over time — green ≥ 75 (Good), gold 60–74 (Needs attention), red < 60 (Intervention).
Throughput vs Commitment
Committed (track) vs completed (fill) per cycle — the widening gap from WK17 on is the over-commitment.
All Cycles
Every reviewed cycle, click to open its full review.
| Cycle | Period | Health | Committed | Done | Completion | Carry-over | Cancelled |
|---|---|---|---|---|---|---|---|
| WK24 | From 2026-06-08 To 2026-06-14 | 77 | 171 | 92 | 53.8% | 78 | 1 |
| WK23 | From 2026-06-01 To 2026-06-07 | 73 | 91 | 45 | 49.5% | 46 | 0 |
| WK22 | From 2026-05-25 To 2026-05-31 | 36 | 100 | 50 | 50% | 48 | 2 |
| WK21 | From 2026-05-18 To 2026-05-24 | 41 | 122 | 67 | 55% | 44 | 11 |
| WK20 | From 2026-05-11 To 2026-05-17 | 28 | 97 | 40 | 41% | 56 | 1 |
| WK19 | From 2026-05-04 To 2026-05-10 | 23 | 100 | 34 | 34% | 66 | 0 |
| WK17 | From 2026-04-20 To 2026-04-26 | 22 | 98 | 34 | 34.7% | 62 | 2 |
| WK15 | From 2026-04-06 To 2026-04-12 | 75 | 63 | 61 | 96.8% | 0 | 2 |
| WK14 | From 2026-03-30 To 2026-04-05 | 67 | 67 | 51 | 76% | 14 | 2 |
| WK13 | From 2026-03-23 To 2026-03-29 | 48 | 73 | 44 | 60% | 27 | 2 |
| WK12 | From 2026-03-16 To 2026-03-22 | 76 | 32 | 30 | 94% | 0 | 2 |
| WK11 | From 2026-03-09 To 2026-03-15 | 82 | 26 | 23 | 88.5% | 0 | 3 |
| WK10 | From 2026-03-02 To 2026-03-08 | 56 | 36 | 24 | 67% | 12 | 0 |
| WK09 | From 2026-02-23 To 2026-03-01 | 79 | 16 | 15 | 93.8% | 0 | 1 |
The schedule story in one line
Healthy, small cycles in Feb-Mar (health 56-82) → the VNPAY onsite pivot (WK17-20) ballooned commitments to ~100/cycle while capacity held, crashing health to 22-28 and piling up 56-66 carry-overs each week → partial recovery in WK21-22 (41→36), then the new delivery-first scorecard from WK23 (73→77). The team ships a steady ~40-92 items/cycle - the collapse was a commitment-discipline problem, not a delivery one. WK16 & WK18 have no recorded review.
Coverage & forward view
One row per cycle that has a recorded Plane sprint review. WK01-WK08, WK16 and WK18 have no review item. WK23-WK24 are scored on the new delivery-first scorecard - not comparable to the older completion-weighted scores (WK09-WK22). The current cycle WK25 (Jun 15-21) is in progress - see the Roadmap. Closed-cycle numbers are the recorded (at-review) figures, not Plane's post-cleanup live counts.
How a sprint review works (the process)
Run at the end of every weekly cycle. The goal is maximum visibility of work, value, progress and blockers - and to keep the board honest. Full agent procedure: .agents/workflows/sprint-review.md.
- Reconcile board vs code first. The board is not ground truth - git is. Audit incomplete items against code and correct mislabeled tickets before scoring.
- Score on a delivery-first scorecard (throughput · flow & aging · predictability · quality · sustainability) - not on commitment-accuracy. Over-commitment is reported as a separate planning signal, never as a low grade.
- Report every dimension, in order: Executive Summary · Scorecard · Value (EBM) · Effort & Contribution · Work Log · Project & Phase Progress · Epic Progress (Phase 2) · Bottlenecks & Flow · Carry-Over · By Module (capability) · By Label · Risks · Trends · Forecast · Action Items.
- Epic Progress reads each Phase-2 epic's child sub-issues (% done) and is synced back to the Phase 2 - Plan so the plan always shows live progress.
- Update one source + publish two homes: the recorded numbers go into
registry/delivery.authored.ts(this dashboard + the hub stat render from it); the wiki page is canonical (bilingual, incl. Executive Summary) →delivery/sprint-reviews/{YEAR}-WK{NN}.md+ sidebar; the Plane item is the mirror (English, labelReport+phase-2, no module).
The Four Phases of the Arc
1 · Foundation
WK09-12 · Feb-mid MarSmall, focused cycles (16-36 items, 67-94% done, health 56-82). Built Casbin RBAC, the Kafka/Debezium CDC pipeline, SMS/OTP, onboarding, and tax/ledger foundations.
2 · Scale-up
WK13-15 · late Mar-AprCycles doubled to 63-73 items. WK13 over-reached (60%, health 48), but WK14-15 stabilised - up to 96.8% completion and health back to 75.
3 · VNPAY pivot crash
WK17-20 · late Apr-mid MayThe team was pulled onto the VNPAY onsite engagement. Commitments ballooned to ~97-100/cycle while real capacity held; completion collapsed to 34-41%, health to 22-28, and carry-over debt exploded to 56-66 each week.
4 · Recovery + rescore
WK21-24 · late May-JunRecord throughput (up to 92 done) but still over-committed; the delivery-first scorecard (from WK23) reframed health to 73→77 - strong delivery, weak age + QA hygiene. ~44-78 carry-overs persist. The fix is commitment discipline, not delivery speed.
How a review is produced
| Step | Action |
|---|---|
| 1. Reconcile | Read every incomplete item and verify against code; fix mislabeled (done-but-open) tickets first |
| 2. Collect | Pull cycle data + git evidence; note which comparison cycles have a trustworthy frozen snapshot |
| 3. Score | 5-dimension delivery-first scorecard (throughput · flow & aging · predictability · quality · sustainability) on the corrected board |
| 4. Report | Executive summary, delivery, team breakdown, carry-over, trend, forecast, action triggers |
| 5. Record | Write the numbers into registry/delivery.authored.ts, publish this page + a Plane Report item (linked from each page) |