Current sprint
Sprint 03
Trip quality and planner trust
Shared command center
Build TripRelay faster without the giant-scroll playbook feel.
This is designed for actual weekly execution, not just reading. Set a sprint goal, plan the week, drag work through the board, track blockers, keep decisions visible, and make release quality obvious before you ship.
Primary focus
Scheduler
Raise must-see hit rate
Release mode
Careful
No blind redeploys
Top risk
Bad POIs
Random filler hurting trust
01
Sprint planning
Keep the sprint goal, success metric, and daily priorities in one visible place.
Editableautosave
Monday
Tuesday
Wednesday
Thursday
Friday
02
Kanban board
Add work, then drag cards across the flow. Keep tasks tight and outcome-based.
Backlog 0
Doing 0
QA / Verify 0
Done 0
03
Quality gates
Make it obvious whether a change is actually safe to ship.
04
Blockers / decisions / retro
Keep the operational reality visible so you do not forget context mid-sprint.
05
Prompt library
Keep the high-value prompts reusable instead of rewriting them every time.
06
Quick operating rules
Make the workbench useful day to day, not just nice looking.
1. One weekly outcome
Do not try to “improve the whole site.” Pick one result and win it.
2. Every card needs acceptance
A task without a testable finish line lingers forever.
3. QA is a lane, not a vibe
Work is not done when coded. It is done when verified against the user experience.
4. Blockers must stay visible
Anything slowing you down should be in the blocker box immediately.
5. Keep prompts versioned
When a prompt works, save it. When it stops working, update it intentionally.
6. Ship with confidence
No deploy if the quality gates are red and you cannot explain why.