definition-of-done

A Definition of Done checklist verifies that a software change is complete across all affected domains, including translations, docs, migrations, accessibility, and tests. It serves as a governance tool for PR readiness and deployment across locales and platforms.

You track cross-cutting requirements by applying a Ripple Map that links changes to required follow-ups. This ensures you map code modifications to necessary updates across translations, documentation, migrations, and accessibility tests before closing a change.

To ensure code changes account for migrations and docs, review the Ripple Map to map the change to required follow-ups. Provide evidence that all affected areas, including documentation and database migrations, are updated before declaring the change done.

Yes, a Definition of Done applies specifically to software development workflows where changes touch multiple domains. It enforces a multi-domain completion mindset, requiring evidence of updates across translations, docs, migrations, accessibility, and tests.

The best way to verify UI tests and translations are complete is using a Ripple Map to map changes to required follow-ups. This governance tool enforces multi-domain completion across all locales before deployment readiness.