Closed from the PowerPoint migration · read-only ·
Locked metrics
Sprint goals completed & sprint velocity
Leading · biweeklyTotal amount of work (in story points) the team completes in a sprint.
Sprint 18: 32 SP
No target
| Value | ||
|---|---|---|
| Sprint 17 | Protected Roles, Configurator changes — velocity not measurednot judged | |
| Sprint 18 | Technical foundations, renewal date integration, Carefinder perf & SEO — 32 SPon target |
Build the AI-native tech company
Lagging · monthlyBuild the data-driven development loop.
3 new foundations shipped
No target
new
new
new
Monthly objectives (max 3)
Prove
Improve time to market
Done means: Business understands tech plans and priorities; tech priorities aligned with business; sync Optix ↔ Admin ↔ HubSpot data; automate PageSpeed analysis; analytics in a closed loop.
Missed
Why: Migrated from PowerPoint — retro not recorded
Decision: drop — Not carried into the next month's deck (migrated)
Scale
Improve the Google PageSpeed Insights results
Done means: Move Stories metrics out of the red zone; Stories locations site into green; Carefinder into green.
Missed
Unblocker
Introduction of the new development process and tech foundations — make tech transparent and predictable for the businessNot achievedHow the framework works — Prove, Scale, Create in plain language
Prove
The car goes from A to B 🚗 — this goal directly moves your KPIs this month.
Scale
Upgrade the road to a highway 🛣️ — makes hitting your KPIs easier in the future.
Create · optional
A great restaurant along the route 🍝 — extra value for members. Optional.
Leading indicator
The number you directly influence — your own steering wheel. If it moves, it's because of what your team did.
Lagging indicator
The result that follows later, often depending on other departments. You can't push it directly — your leading work pushes it for you.
The tsunami rule: when your leading and lagging KPIs are both behind, do more Prove and stop Scale. You don't renovate the kitchen when a tsunami is coming. 🌊