Do you really need a long definition of done? We in Adform think not!
We are always trying to improve process and they way of working, but don’t forget to hire great people.
Here is the reminder from Steve Jobs (RIP) about importance of great employees! (from fastcompany.com)
Understanding these simple things help me in my daily work.
1. It’s impossible to gather ALL the requirements
2. Whatever requirements you have are guaranteed to change
3. There is always more to do than you have time and money allow
So, it’s only left to convence customers and developers that you can do nothing about it. And we must work together flexibly to make our lives a bit easier 
When someone tries to start using Scrum inevitably there are a lot of discussions about definition of done. You will hear a lot of things starting from design documents and ending with unit tests. But it becomes very obvious what must be included into definition of done when you imagine something not related with software.
Imagine a situation that you decided to paint you room with a new color. Since you are not able to do this by yourself (it might not be a case in your situationJ) you are going to hire external specialists. So, these specialists return to you in two weeks with following output:
- Elegant design of the room
- Report how they planned to paint the room
- Analysis of different colors
- Half painted room with low quality
- Tools scattered around
Are you going to be happy as a customer? Is this what you want? So, when you are going to have a discussion about definition of done, please take real value into account first and don’t forget the quality.
p.s. despite the common sense discussions about definition of done are always quite difficult and it is not so easy to come to a common agreement.
Each scrum master presents a hot topic for his team during the retrospective of retrospectives.
It leads to very interesting discussions and better understanding of the topic.
How do you do it in yours scrum adoption?
Top 200
LinkedIn
Twitter