UNITED WAY STL ACADEMY
  • Courses
  • Log In
  • Join Free
  • Home
  • Courses
  • Scrum Essentials

The Part of Tens

Curriculum

  • 3 Sections
  • 30 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • Ten Key Benefits of Scrum
    10
    • 1.1
      Higher Customer Satisfaction
      10 mins
    • 1.2
      Better Product Quality
      10 mins
    • 1.3
      Reduced Risk
      10 mins
    • 1.4
      Improved Performance Visibility
      10 mins
    • 1.5
      Increased Investment Control
      10 mins
    • 1.6
      Increased Collaboration and Ownership
      10 mins
    • 1.7
      More Relevant Metrics
      10 mins
    • 1.8
      Improved Predictability
      10 mins
    • 1.9
      Optimized Team Structures
      10 mins
    • 1.10
      Higher Team Morale
      10 mins
  • Ten Key Factors for Enabling Scrum
    10
    • 2.1
      Dedicated Team Members
      10 mins
    • 2.2
      Collaborative Environment
      10 mins
    • 2.3
      Done Means Releasable
      10 mins
    • 2.4
      Empowered Product Owner
      10 mins
    • 2.5
      Donโ€™t Ignore Reality
      10 mins
    • 2.6
      Clear Product Goal and Roadmap
      10 mins
    • 2.7
      Developer Versatility
      10 mins
    • 2.8
      Scrum Master Clout
      10 mins
    • 2.9
      Leadership Support for Learning
      10 mins
    • 2.10
      Leverage Industry Experts
      10 mins
  • Ten Key Resources for Scrum
    10
    • 3.1
      Scrum For Dummies Cheat Sheet
      10 mins
    • 3.2
      The Scrum Guide
      10 mins
    • 3.3
      Scrum Alliance
      10 mins
    • 3.4
      Agile Alliance
      10 mins
    • 3.5
      Business Agility Institute
      10 mins
    • 3.6
      State of Agile Report
      10 mins
    • 3.7
      ScrumPLoP
      10 mins
    • 3.8
      Certification Resources
      10 mins
    • 3.9
      Scaling Scrum Resources
      10 mins
    • 3.10
      Platinum Edge
      10 mins

Done Means Releasable

Scrum For Dummiesยฎ โ€” The Part of Tens

Done Means Releasable

๐Ÿ• 12 min read
The Big Question

What does it truly mean for a product increment to be “done” in Scrum, and why does this matter for agile success?

Scrum teams often talk about โ€œdone,โ€ but what does that really mean? In the world of agile, the difference between โ€œdoneโ€ and โ€œalmost doneโ€ can determine whether a sprint achieves its purpose โ€” and whether the team continues to improve. This lesson unpacks why only potentially releasable increments count as truly โ€œdone.โ€

Done Means Releasable

Ending sprints with nonreleasable product increments is an antipattern to becoming more agile. Done means potentially releasable. A sprint that ends without potentially releasable functionality is, by definition, not a sprint.

Developers get to done by swarming on user stories โ€” working together on one user story at a time until it is complete before starting the next. Developers hold each other accountable by ensuring that all rules for their definition of done, including test automation, are satisfied before starting a new user story. Product owners review completed work against the scrum teamโ€™s definition of done (as well as the user storyโ€™s acceptance criteria โ€” see the module on user stories) before approving and moving on to a new user story.

๐Ÿ’ก Did You Know?

The term “antipattern” refers to a common practice that looks appealing but undermines agile principles. Ending sprints with nonreleasable increments is a classic antipattern in Scrum.

Definition of Done

A shared agreement within the Scrum team that specifies the rules, quality criteria, and requirements a user story or increment must meet to be considered complete.

Potentially Releasable Increment

An increment that meets all requirements and quality standards so it can be released to users immediately, if the Product Owner chooses.

In a software company, teams often finish sprints with features that are “almost working.” These features may pass basic tests, but if they aren’t integrated, documented, and fully tested, they can’t be released. Only increments that are fully ready โ€” tested, documented, and integrated โ€” are considered “done” in Scrum.

Want to go deeper? The science behind “done” in agile teams

Research into high-performing agile teams shows that clear, enforceable definitions of โ€œdoneโ€ reduce ambiguity and build trust. When teams know exactly what counts as โ€œdone,โ€ they spend less time arguing, more time collaborating, and produce higher-quality, releasable code. Test automation and peer accountability are proven drivers for reaching this standard.

โฑ 5 minutes
Activity: Define “Done” For Your Team

Work with your team (or imagine one) to create a definition of “done” for a single user story.

  1. List the criteria that must be met for the story to be considered complete (e.g., code reviewed, tests automated, documentation updated).
  2. Compare your list with your teammates. Are there any gaps or disagreements?
  3. Revise the definition together to ensure everyone agrees.

Ending sprints with nonreleasable product increments is an antipattern to becoming more agile.

โŒ Common Misconception

Anything that passes basic tests or is “almost done” counts as a finished sprint increment.

โœ… The Reality

Only increments that are potentially releasable โ€” meeting all criteria in the definition of done โ€” are truly “done” in Scrum.

How would your teamโ€™s workflow change if you enforced a stricter definition of “done”?

What risks arise if a sprint delivers features that arenโ€™t ready for release?

Think of a time when you or your team considered a task “done” but later found gaps or issues. What would have been different if you had used a strict, shared definition of done?

0 words Take your time โ€” depth matters more than length

Experienced Scrum practitioners recommend swarming on user stories โ€” the team works together to finish one story before starting another. This approach ensures all aspects of the definition of done are met, and prevents unfinished work from piling up.

Flashcard

What is the “definition of done” in Scrum?

Tap to reveal
Answer

A shared agreement specifying the rules and quality standards required for work to be considered complete.

Flashcard

Why must a sprint increment be potentially releasable?

Tap to reveal
Answer

Because only releasable increments fulfill the purpose of a sprint and support continuous delivery and improvement.

Flashcard

What is an antipattern in Scrum?

Tap to reveal
Answer

A common but harmful practice, such as ending sprints with nonreleasable increments.

+50 XP

In Scrum, what does “done” mean for a product increment?

Review the “Done Means Releasable” section above to find the answer.
  • Learned the importance of a clear definition of done
  • Understood why only potentially releasable increments count as done

How does swarming on user stories help teams achieve โ€œdoneโ€ status?

Key Takeaway

In Scrum, “done” means potentially releasable โ€” only increments meeting all criteria can be considered complete and ready to deliver.

Key Takeaway

Swarming on user stories and holding each other accountable to the definition of done ensures quality, collaboration, and continuous improvement.

SHIFT

The Shift

  • A sprint is only complete when the increment is potentially releasable.
  • Clear definitions of done and team accountability prevent unfinished work from accumulating.
  • Swarming on user stories drives collaboration and ensures every increment is truly โ€œdone.โ€
End of lesson Ready for the next lesson?
Continue to next lesson ย โ†’

Leave a Reply Cancel reply

Collaborative Environment
Prev
Empowered Product Owner
Next

ยฉ 2026 United Way STL Academy | Powered by Sejal Learning Systems.

Modal title

Main Content