Sprint Review - WK26
Cycle 2026-06-22 → 06-28 · Recorded in Plane as BANA-1706. 184 work items · 40 done · 21.7% completion.
In one line
A high-effort cycle whose results are stuck before the finish line: most of the work is finished, but waiting on QA acceptance and deployment, so only 22% is formally "done". Clearing that acceptance queue is the single most important action for next cycle.
Executive Summary
The team delivered a strong volume of work this cycle, but very little of it crossed the formal finish line. Of the 184 items in the cycle, 40 are done (22%) - the lowest completion rate in the tracked window.
The reason is not a slowdown in delivery. 80 of the 89 in-flight items are already finished; they are sitting in a "ready for QA" or "ready to deploy" state, waiting on acceptance and release. Only nine items are genuinely still being worked on. Until those 80 items are tested, accepted, and deployed, they do not count as done - which is why the completion number understates what was actually produced.
Two housekeeping issues make the number look worse than it is: the cycle was oversized (184 items vs a healthy ~40), and 25 leftover items from Phase 1 are still sitting in the cycle with no chance of completing here.
Bottom line: delivery capacity is healthy; the constraint is the acceptance-and-release pipeline. The priority is to drain the 80-item "ready" queue and right-size the next cycle.
Delivery Scorecard
A balanced view across five dimensions, rolled up into one health score.
| Dimension | Score | Reading |
|---|---|---|
| Throughput | 68 | 40 items accepted, below the recent typical of ~59 per cycle |
| Flow & Aging | 61 | 56 of 143 open items (39%) have aged beyond two weeks |
| Predictability | 68 | delivery volume continues to swing cycle to cycle |
| Quality | 78 | almost nothing cancelled; all QA verification cleared |
| Sustainability | 65 | workload is spread across the team; the squeeze is at acceptance, not the build |
| Delivery Health | 67 - Needs attention | weighted roll-up of the five |
Two planning signals (reported separately): the cycle held 4.6× more work than is sustainable (184 vs ~40), and completion was 21.7%, held down by the acceptance queue and the leftover Phase-1 items.
What We Delivered
Value that landed or advanced this cycle, in business terms:
- Merchant growth analytics for the operations team - a growth report and distribution dashboards in the Backoffice, giving the team visibility into merchant performance and revenue.
- Helpdesk improvements - clearer ticket ownership and follower rules, plus file attachments, making support cases easier to track and resolve.
- A new mobile app foundation for shop owners - the groundwork for a dedicated mobile experience, including the sign-up/onboarding flow.
- Vietnamese across the product - a full localization pass so the product reads naturally for Vietnamese merchants and staff.
- Point-of-sale shift & receipt printing - shift handling and receipt printing for the sales floor.
- Platform reliability - behind-the-scenes search, data-sync and deployment improvements that keep the system fast and stable as it scales.
Why Completion Looks Low
This is the most important thing to understand about the cycle.
| Stage | Items | Meaning |
|---|---|---|
| Done | 40 | tested, accepted, deployed - counts as complete |
| Built, awaiting acceptance | 80 | finished, sitting in QA / ready-to-deploy |
| Still in progress | 9 | genuinely being worked on |
| Not started / on hold | 55 | queued or parked |
The 80 "built, awaiting acceptance" items are real, finished work - they simply have not been pushed through the final QA-and-deploy step. This is the bottleneck, and clearing it is where the biggest gain lies next cycle. It needs a clear acceptance-and-release routine (a defined hand-off from "finished" to "tested" to "live"), not more building.
Epic Progress (Phase 2)
Directional progress against the Phase-2 roadmap. Most of this cycle's movement is work that is built and waiting on acceptance, so it advances the picture without yet flipping items to fully done.
| Epic | Owner | Progress | Note |
|---|---|---|---|
| Backoffice portal (merchant ops) | Hai / Phat | 65% → 72% | growth analytics + dashboards landed |
| Point-of-sale selling experience | Hai / Khoa | 58% → 62% | cart, receipts, mobile groundwork |
| Permissions & user administration | Phat / Hai | 80% → 82% | per-merchant access continuing |
| Sales shift management | Viet / Phat | 90% → 92% | receipt + shift polish |
| Kitchen & self-order | Hai / Khoa | 15% → 18% | early, ramps in August |
The long poles - Customer (tax ID), Inventory, and general Retail - remain flat and are scheduled to start in July. They carry the most schedule risk for the September target and still need assigned business owners.
Risks & Decisions Needed
| Risk | Why it matters | What we're asking |
|---|---|---|
| 80 items stuck before "done" | effort isn't converting into shipped value; completion looks artificially low | agree and run an acceptance-and-release routine; clear the queue first |
| Oversized cycle (4.6×) | dilutes focus and makes progress hard to read | size the next cycle to ~40 committed items |
| 25 stale Phase-1 leftovers | inflate the cycle and depress completion | clear them out of the Phase-2 cycle |
| Aged backlog (56 items > 2 weeks) | erodes predictability | review and split or cancel the oldest items |
| Customer / Inventory / Retail not started | these are the reason Phase 2 exists; September target at risk | assign business owners and start in early July |
Trends (6-cycle)
| Metric | WK21 | WK22 | WK23 | WK24 | WK25 | WK26 | Direction |
|---|---|---|---|---|---|---|---|
| Items done | 67 | 50 | 45 | 92 | 86 | 40 | ▼ |
| Completion % | 55% | 50% | 49.5% | 53.8% | 36.4% | 21.7% | ▼ |
| Carried over | 44 | 48 | 46 | 78 | 142 | 143 | ► |
| Delivery Health | 41* | 36* | 73 | 77 | 80 | 67 | ▼ |
* WK21-22 used an older scoring scale and are not directly comparable.
The dip this cycle is driven by the acceptance bottleneck and the oversized backlog, not by a drop in the team's output. Resolve the acceptance queue and the next reading should recover.
Forecast
| Milestone | Confidence (50%) | Confidence (85%) |
|---|---|---|
| Clear the "built, awaiting acceptance" queue | early July | mid-July |
| Backoffice portal + shift management complete | mid-July | late July |
| Kitchen & self-order | August | late August |
| Customer / Inventory / Retail | August | late August |
Assumes the acceptance-and-release routine is in place, the next cycle is right-sized, and the Customer / Inventory / Retail epics get owners in early July.
Action Items
- Stand up an acceptance-and-release routine and clear the 80-item "ready" queue - Phat / Le Linh (the top priority)
- Size the next cycle to ~40 items and drain carry-over first - Phat
- Remove the 25 leftover Phase-1 items from the Phase-2 cycle - Phat
- Review and trim the aged backlog (56 items over two weeks) - Phat
- Assign owners and start Customer, Inventory and Retail in early July - Phat / Hai
Related Pages
- Sprint Reviews · Roadmap · Phase 2 Plan · Traceability Matrix
- Plane: BANA-1706 (Report)