Done Criteria

A shared set of completion standards that apply to every user story. A clear, agreed Definition of Done reduces ambiguity and ensures the team meets required quality practices. These standards are established when creating the prioritized product backlog. A user story counts as done only after it is shown to the Product Owner and accepted against the Done Criteria and the story-specific acceptance criteria.

Key Points

  • Common checklist for all user stories that defines minimum completeness and quality.
  • Removes ambiguity, aligns expectations, and reduces rework.
  • Typically covers code, tests, reviews, integration, documentation, and deployability.
  • Used by the Product Owner to accept work; distinct from story-level acceptance criteria.

Example

A Scrum team defines Done Criteria: code peer-reviewed, unit tests at 80% coverage and passing, integrated to main branch, updated user documentation, security checks passed, and acceptance criteria met. At sprint review, the team demos a story; the Product Owner verifies these Done Criteria plus the story's acceptance criteria before accepting it.

PMP Example Question

Which statement best describes Done Criteria in an agile project?

  1. A list of tasks in the sprint backlog for a specific story.
  2. A shared definition of completion that applies to all user stories.
  3. The acceptance criteria written by the Product Owner for one story.
  4. A release plan describing how increments are deployed to production.

Correct Answer: B — A shared definition of completion for all stories

Explanation: Done Criteria are the common standards used to judge whether any user story is complete, while acceptance criteria are specific to a single story.

ICS/OT Incident Drills and Tabletop Exercises

An incident response plan is only a theory until the people who must use it have run it under pressure. This course helps OT engineers, operations leaders, IT responders, and security teams turn a plan on paper into a tested capability.

Define safe states and manual fallback before an incident forces the decision. Build escalation paths, tabletop exercises, and scenarios that expose the gaps a document review cannot find.

Then turn the results into evidence: an after-action report, owned improvements, recovery checks, and a drill cadence that keeps the program alive after the exercise ends.

51 lessons, 4.8 hours of video, eight quizzes and four hands-on assignments. US$47 one-time through HKSM Courses. 30-day money-back guarantee when 50% or less consumed.

Explore the Course


ICS/OT Incident Drills and Tabletop Exercises course preview

Build an ICS/OT cybersecurity foundation that fits the real environment

Standard IT controls can disrupt the industrial systems they are meant to protect. Learn how to assess OT risk, design zones and conduits, apply IEC 62443 security levels, use MITRE ATT&CK for ICS, and establish passive asset visibility without risking production. Eight reconstructed incidents connect attacker techniques to the controls that failed, giving you the vocabulary and judgment to make credible security decisions from day one.

Explore the Course