Definition of Done in Scrum: Free Course

About this course

A task can be marked complete while the product still cannot be used. This free short course explores how a Definition of Done makes product quality visible and helps a Scrum Team agree on what a usable Increment really means. Six focused videos from Scrum.org examine completed work, acceptance criteria, technical debt and the practical task of creating a shared quality standard.

Course at a glance

What you’ll learn

• Explain how a Definition of Done makes the quality and completeness of an Increment transparent, so that a team can discuss finished work using shared expectations.
• Distinguish the product-wide Definition of Done from acceptance criteria for an individual Product Backlog item, and recognise why satisfying one does not automatically satisfy the other.
• Examine the difference between technical debt and work that does not meet the Definition of Done, rather than treating every unfinished quality activity as the same problem.
• Prepare a first draft of a Definition of Done that describes observable quality conditions and gives the team a concrete starting point for discussion and improvement.

Skills you’ll gain

• Definition of Done
• Increment quality
• Acceptance criteria
• Quality transparency
• Technical debt awareness
• Team agreements

Course Overview

The course concentrates on one practical Scrum concept rather than attempting to cover every aspect of agile delivery. It starts with the meaning of a Done Increment, then places the Increment and its quality commitment within the Scrum framework. The following explanations compare acceptance criteria with the Definition of Done, consider technical debt and unfinished work, and finish with guidance on crafting a Definition of Done.

All six videos from the source playlist are included in their original sequence. Two lessons discuss the relationship between acceptance criteria and the Definition of Done from different perspectives; both remain available because the second explanation can help reinforce the distinction. The original lesson titles are preserved, including the numbered series title of the second video.

Three ideas to carry into your work

• Make quality inspectable. Replace vague statements such as “looks finished” with conditions that a team can check and explain.
• Separate item-specific requirements from shared product quality. A feature’s desired behaviour and the standards for a usable Increment answer related but different questions.
• Use the agreement to guide conversations. A Definition of Done helps expose gaps in capability, testing or integration that otherwise remain hidden until work reaches a customer.

Who is this for?

This course suits new Scrum Masters, Product Owners, Developers, testers and project professionals moving toward product delivery. It is also useful for teams that regularly disagree about whether work is finished, discover quality problems late, or rely on an informal checklist that different people interpret differently. Experienced practitioners can use the short explanations as a focused refresher before a team conversation about quality.

Before you start

A basic awareness of Scrum terms such as Sprint, Product Backlog and Increment is helpful. You do not need a paid tool or specialist software to follow the videos. Bring a notebook and, if possible, an example of a small product or feature so that you can connect the explanations to work you understand.

Put the lessons into practice

Choose a small product change, such as an improved search feature or a new account-setting screen. Write two separate lists. In the first, describe the specific behaviour that would satisfy the feature’s acceptance criteria. In the second, draft the quality conditions that every Increment of that product should meet. Consider relevant checks such as successful integration, appropriate testing, security review or required documentation, rather than copying a generic checklist without considering the product.

Review each condition and ask what evidence would show that it has been met. If a condition cannot be checked, make its wording more precise. Then identify one gap that the team would need to address to meet the draft consistently. This is an optional WikiFree study activity, not an assessed assignment from Scrum.org. Its purpose is to turn the videos into a useful conversation and a working draft, rather than a certificate exercise.

Certificate / Assessment

The videos are free to watch directly in this classroom. This course does not include a Scrum.org certification, an exam voucher or instructor assessment. Marking lessons complete records your learning progress; it does not demonstrate professional competence or award a qualification.

Frequently asked questions

Provider: Scrum.org. Videos play from the Scrum.org channel on YouTube.