Share via

Definition of Done

  • Article

Your favorite agile literature probably talks about the importance of defining what done means so everybody (team and product owner if we use Scrum terms) knows what we mean when we say something is done. And having a catchy acronym to remember what your definition of done is is in my opinion a good thing.

When I did my Scrum certification a few years ago I learned an acronym that was a suggestion for what done meant. The catchiness in this acronym is that it is the Swedish word for done:

Kodat - Coded/Implemented

Levererat - Delivered/checked-in/published

Accepterat - Accepted i.e. solved according to agreement
Redovisat - Documented

Tested - By developers and QA

So translating this to CDADT or IDADT isn't really that catchy in my opinion. My current team came up with a different acronym without really looking at the Swedish example. The result:

Designed - discuss design/solution with peer(s)

Implemented - for code: coding guidelines including comments apply

Reviewed - Solution reviewed before check-in

Tested - work with QA to make sure team tests everything QA wants team to test but not things QA will test anyway.

Now that's a catchy acronym in my opinion! Especially since it is supposed to increase quality. Irony is so funny in my opinion...

Comments

  • Anonymous
    April 07, 2011
    I have been given the job of translating a powerpoint document from Swedish to English (which is a real pain) and came to a slide with this Swedish acronym and was wondering what to do with it. I googled "Definition of Done ackronym" and hey presto. I didn't expect to get such a direct hit! Thanks!!