Skip to main content

Not Done, not Scrum! Why you can't create value and manage risks without Done Increments.

February 14, 2022
Not done is like serving a raw chicken burger

Summary (TL;DR;)

  • If you can't create Done Increments every Sprint, this is the #1 issue to fix!
  • Done means more than what is written in the Scrum Guide
  • Without Done Increments, you won't get any benefits from Scrum
  • You need Done Increments to capture product value
  • You need Done Increments to manage the 3 product development key-risks
  • A Definition of Done first and foremost describes quality, not just work
  • A well-structured DoD creates transparency, commitment and quality
  • There's a way to fix this problem and create a great Definition of Done

 

Introduction

"Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems."1 Scrum Teams generate value by creating and delivering Done Increments.

Now, the inconvenient truth is that most Scrum Teams do not create Done Increments regularly, meaning one or more Increments every Sprint. Based on our experience as Professional Scrum Trainer (PST), Scrum Masters and Product Owners, we can say that about 7 of 10 Scrum Teams don't create Done Increments regularly. This is a serious issue!

Why? If your Scrum Team has this problem, you will not get any benefit from using Scrum. For example, you will not be able to maximize product value and manage the 3 key-risks of product development. In fact, if you have this problem, it is the first thing you need to fix!!

In this article, we will explain why not creating Done Increments regularly is a serious issue and how you can solve it.

Read the full article here.

 


What did you think about this post?

Comments (4)


Leini
09:17 am February 22, 2022

Hi Johannes,
how can we measure value if our goal is a MVP? (We do not release the increment to the user, before we have not reached MVP.)
Thanks in advance!


Johannes Geske
02:26 pm February 23, 2022

Hi Leini! Can you give an example of what MVP means to you? To me, an MVP is an experiment to test a hypothesis, such as whether users will see value in a new product or feature. In this example, the value would be to learn from users whether they actually like it or not.


Leini
06:57 pm February 23, 2022

Hi Johannes,
1. example: new Webshop MVP
As an agency we create a new webshop for company that already has a webshop. Therefore the company has set 80% of the current features as MVP, since they know that the users need them. So we built this new webshop but with a new design. We build 1 year and then we release to production to test. So when shall we test value?
2. example: new DKB App
Maybe you know the bank DKB. They created a native app since there was only a web app available. The web app had a lot of features since it was the website. The new app is more a MVP since it has more or less 30% of the features and the review are quite bad on google play store. So, the DKB went with a MVP test but have a bad review app review and probably a lot of customer tickets. So, they released early to test quickly but lost customer satisfaction. So, when would be the best release time?


Johannes Geske
08:29 am February 24, 2022

#1 As a Product Owner I'd be interested in testing my assumptions about value as early as possible in order to manage risks. If I already have empirical prove that we have to create x amount of product capabilities before we can deliver value to users, the risk of delivering a product that wouldn't be valuable is managed. However, as user needs and market conditions change, I'd always be interested in delivering early and frequently in order to stay empirical.

#2 Time is one thing to consider. The delivery strategy (for example, delivery to all users vs. delivery to few select users) is another thing to consider and learn more about the value of an early product.