Definition of Done, QA, and Documentation | Free Lesson

This lesson gives you a six-layer definition of done and a worksheet you can adapt to a real work item without exposing confidential details.

Lesson details: 45 minutes · on-demand written lesson and practical artifact · developed and reviewed by IT Modality Academy.

Different people can mean different endpoints.

An engineer may mean the change is built. QA may mean the agreed tests pass. An operator may mean monitoring and support are ready. A client owner may mean the outcome is accepted. Documentation may still be missing from every version.

A useful definition of done joins these perspectives before work begins. It does not require every possible check; it requires the checks relevant to the risk and outcome.

1. Scope

• Included behavior or work product is named.

• Exclusions and deferred items are recorded.

• Approved change requests are incorporated.

2. Acceptance

• Acceptance criteria are observable.

• The acceptance owner is named.

• Unresolved interpretation is decided or explicitly open.

3. Quality and test evidence

• Relevant positive, negative, boundary, regression, integration, or operational checks are defined.

• Results and exceptions are recorded.

• Defects are resolved, accepted, or deferred by an authorized owner.

4. Documentation

• The right audience can understand configuration, use, support, decision history, and known limits.

• Links point to the current source, not a detached copy.

• Confidential information is kept in the approved location.

5. Operational readiness

• Access, deployment/change, monitoring, support, rollback, and escalation needs are addressed where relevant.

• Owners know what to watch and what to do when the state changes.

6. Handoff and closure

• The receiving owner accepts the artifact or state.

• Open items have owners and checkpoints.

• Evidence remains discoverable after the project conversation ends.

Quality assurance begins before test execution.

Ask:

• Which failure matters most?

• Which assumption is least tested?

• Where can data, workflow, access, or environment differ?

• What evidence would reveal an incomplete result?

• Which issue requires a decision rather than another test?

• What remains true only under a stated limitation?

Testing can show what was checked under defined conditions. It cannot prove that every defect is absent. State coverage and limits honestly.

Document for a future decision, not for the existence of a document.

A useful record answers:

• What is this?

• Why was this path chosen?

• Who owns it now?

• How can someone verify its state?

• What should they not assume?

• What changes require review?

• How can they recover or escalate?

Prefer a short current record over a large abandoned manual. Name the owner and review trigger.

Work item: Add an approved validation rule to a test reporting flow.

Done means:

• rule behavior and excluded cases are documented;

• approved samples pass and negative samples fail as expected;

• regression checks show existing approved rules still behave as recorded;

• the exception is visible in the support runbook;

• the product owner accepts the test evidence; and

• the deployment/handoff record names the monitoring and escalation owner.

Known limitation: The example covers the test flow only; production scale and a new source format are outside scope.

This example is invented and demonstrates the worksheet. It is not evidence of a client release, quality rate, or outcome.

Definition-of-Done Worksheet

Work item/outcome:
Included scope:
Excluded/deferred scope:
Acceptance owner:
Acceptance criteria:
Risk-based checks:
Test environment/data boundary:
Evidence location:
Defects/exceptions and disposition:
Documentation required/audience:
Access/change/deployment readiness:
Monitoring/support/escalation:
Handoff owner:
Known limitations:
Final decision/date:

Ask the builder, reviewer, and receiving owner to mark the worksheet separately. Any disagreement is a requirement or decision gap—not a reason to hide behind the word “done.”

Fallback: “Developed by IT Modality Academy.” Named/credential material suppressed until approval.

Next: delivery tools in context

Continue to delivery tools Previous Index Related bootcamp

Firewall: Lesson/signup do not affect The Rigors or work. See /legal/training-work-firewall.