Fadi Stephan - Definition of Done Canvas
Playback access may have expired or the stream is unavailable. Reload the page to request fresh access.
Another tab is open for this lesson. You can keep watching here; the newest position wins.
Saved position may be approximate: the browser clock disagreed with the server.
Your free preview has ended
Create a free account to finish this lesson, or subscribe for the full library.
Your viewing record
No viewing recorded yet. Press play; your position is saved about every 10 seconds.
Last viewed . Last position —.
Completion
Based on 0:00 of unique watched video. Repeats and skipped parts do not increase it.
Many Scrum teams still struggle with delivering high-quality, fully tested, production-ready product increment at the end of each Sprint.
Most still approach product development the traditional way and go through several Sprints without delivering and then have a special Sprint in which they integrate, test, and prep everything for deployment. These teams likely have a weak Definition of Done.
The Definition of Done is an often misunderstood or overlooked concept in Scrum. Most teams don’t formally have one and confuse it with the Acceptance Criteria.
Come to this session to learn about how to create a Definition of Done and then use the Definition of Done Canvas in your retrospectives to gradually strengthen your Definition of Done and continuously improve the quality of your product increment so that your teams can deliver a potentially shippable product increment at the end of each Sprint.
Comments (0)
Log in to join the discussion.
No comments yet. Be the first to comment.