Pathwise

Manuals / Agile & Scrum / Chapter 7

C · Quality gates · intermediate · Week 3 · Chapter 7 of 10

Definition of Done that bites

DoD is the quality contract for every Increment. If “tested” is vague, bugs escape. Make DoD checkable and shared.

Path progress
65%

Step 1 of 2

Draft a real DoD

Include: code reviewed, tests at agreed level, a11y/security notes if relevant, docs/runbook updates, deployed to staging.

  • Acceptance criteria met
  • Unit/integration/E2E as agreed for the change
  • No new Sev-1/2 known issues
  • Feature flag / rollback path if needed
  • Observability: log/metric/trace touch if user-facing
Draft a real DoDDrag 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 →Draft a real DoDdrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Write a 6–10 item DoD checklist your team could adopt next sprint.

Was this step clear?
Chapter learning outcomes
  • DoD vs acceptance criteria
  • Team vs org DoD
  • Undone work

Clear these before you leave