Sprint: FE Sprint 11
Dates: 2026-06-11 → 2026-06-22
Goal: (active sprint — data as of 2026-06-16, mid-sprint)
Report Generated: 2026-06-16
| Metric | Value |
|---|---|
| Issues Closed (Sprint 11) | 22 |
| Issues Opened (Sprint 11) | 16 |
| Net Burn (Sprint 11) | +6 |
| Open Backlog | 196 |
| Avg Issues Closed (4 sprints) | 52.5 |
| Avg Net Burn Rate (4 sprints) | +1.75 |
Note: Sprint 11 is mid-sprint (5 of 11 days elapsed). Final numbers will be higher.
| Sprint | Closed | Opened | Net |
|---|---|---|---|
| Sprint 8 (Apr 29 – May 13) | 46 | 58 | -12 |
| Sprint 9 (May 13 – May 28) | 70 | 59 | +11 |
| Sprint 10 (May 28 – Jun 11) | 72 | 70 | +2 |
| Sprint 11 (Jun 11 – Jun 22)* | 22 | 16 | +6 |
* Sprint 11 is in progress — numbers are partial.
| Priority | Open Count |
|---|---|
| Highest | 7 |
| High | 43 |
| Medium | 124 |
| Low | 19 |
| Lowest | 3 |
| Total | 196 |
xychart-beta
title "Issues Closed vs Opened"
x-axis ["Sprint 8", "Sprint 9", "Sprint 10", "Sprint 11*"]
y-axis "Issues" 0 --> 80
bar [46, 70, 72, 22]
bar [58, 59, 70, 16]
xychart-beta
title "Net Issues per Sprint"
x-axis ["Sprint 8", "Sprint 9", "Sprint 10", "Sprint 11*"]
y-axis "Net" -15 --> 15
bar [-12, 11, 2, 6]
xychart-beta
title "Estimated Open Backlog Trend"
x-axis ["Sprint 8", "Sprint 9", "Sprint 10", "Sprint 11*"]
y-axis "Open Issues" 150 --> 220
line [208, 197, 196, 196]
pie title "Open Issues by Priority"
"Highest" : 7
"High" : 43
"Medium" : 124
"Low" : 19
"Lowest" : 3
-
WIN: Velocity has increased significantly — Sprint 9 (70) and Sprint 10 (72) nearly doubled Sprint 8 (46). The team hit a strong cadence during the Bug Scrub and Polish phases.
-
WIN: Sprint 11 is on pace — 22 closed in ~5 days projects to ~44–48 by sprint end, maintaining strong velocity.
-
TREND: Inflow has been high (58–70 issues/sprint) through Sprints 8–10, reflecting active bug discovery during polish. Sprint 11 inflow appears lower (16 so far), suggesting the bug discovery wave may be subsiding.
-
RISK: 7 Highest-priority issues remain open. These include a memory leak (FE-267), analytics inconsistencies (FE-506, FE-261), and other critical items that should be resolved before launch.
-
NOTE: The backlog has stabilized at ~196 issues. At the current average net burn rate of +1.75/sprint, the active backlog would take ~112 sprints to clear — however, the Low/Lowest tier (22 issues) contains long-standing feature ideas unlikely to be prioritized near-term.
-
WIN: Key completions this sprint include email notification settings (FE-617–619), calendar filter state exposure (FE-558), energy chart polish (FE-562), link dialog polish (FE-535), tooltip hover improvements (FE-518), and a long-standing memory leak fix (FE-267).
| Key | Summary |
|---|---|
| FE-619 | DEV: Custom redirect for Manage email preferences link |
| FE-618 | DEV: Remove deprecated summary email preference fields from client |
| FE-617 | DEV: Design Your Week toggle in email notification settings |
| FE-616 | DEV: Design mode deeplink from Design Your Week email |
| FE-615 | DEV: Optically balance visible data range on grid |
| FE-614 | DES: Edit Form IA updates |
| FE-605 | DEV: Deep-linking to events from Search doesn't close overlays |
| FE-602 | DEV: Energy Block Mock Data Issue |
| FE-600 | DEV: Further tweaks to Sean Ellis copy |
| FE-598 | DEV: Improve grid "date" alignment |
| FE-574 | DES: Time Block Coachmark (Post-FTUE) |
| FE-564 | DEV: Mobile menu cleanup |
| FE-562 | DES: Energy Chart Polish |
| FE-561 | QA: Regression Testing Doc |
| FE-558 | DES: Expose filter state in explorer panel when applied |
| FE-535 | DEV: Polish link entry dialog |
| FE-518 | DEV: Global Tooltip Hover Delay and Scrubbing State |
| FE-491 | DEV: Pull out some more visual widgets into testing view for Marketing/Production |
| FE-487 | DEV: Alignment Graphic Light Mode |
| FE-466 | DEV: Desktop: Improve Snackbar Visibility in Busy Calendar Views |
| FE-267 | Data Explorer: App crashes after switching weeks 4-5 times — likely memory leak |
| FE-164 | DEV: Quick Add dropdown not appearing on first "tap" (not drag) after a fresh reload |
| Metric | Value |
|---|---|
| Avg Velocity (completed sprints 8–10) | 62.7 issues/sprint |
| Avg Net Burn (completed sprints 8–10) | +0.3 issues/sprint |
| Open Backlog | 196 |
Caveat: The net burn rate is near zero because inflow roughly matched throughput during active bug discovery. As inflow decreases (Sprint 11 trend suggests this), net burn should improve. The backlog also includes ~22 Low/Lowest items that are long-term feature ideas, not launch-critical work.