Manuals / Work Tracking / Chapter 4

A · Tickets · intermediate · ~30 min · Chapter 4 of 9

Bugs vs stories vs chores

Story = user value. Bug = broken expectation. Chore/task = maintenance. Mislabeling warps metrics and priority.

Path progress
44%

Step 1 of 1

Sorting hat

“Never built” usually isn’t a bug. “Used to work” usually is.

  • Bug — unintended behavior vs documented/prior behavior
  • Story — new or changed user-facing value
  • Chore — refactor, dependency bump, CI flake fix
Sorting hatDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Sorting hatdrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Sort 10 recent tickets into bug/story/chore. Fix 2 mislabels.

Was this step clear?
Chapter learning outcomes
  • Type heuristics
  • When a bug is a story
  • Tech debt tickets

Clear these before you leave