Blog Post
Why Scrum Requires Completely “Done” Software Every Sprint
November 27, 2018
In Scrum, “Done” doesn’t support adjectives like “nearly”, “pretty much” or “almost”. Work is “Done” or it isn’t . And there is a very powerful, compelling reason behind this: the Scrum Framework only helps to reduce the risk of wasting money and effort when you deliver “Done” software every Sprint; a new version of your product that is, or with the proverbial press of a button can be, released to users. In this post I underscore how essential this rule is to Scrum.