Multiple levels of done and design

The definition of done is core to agile but can you have multiple levels of done? I came across this blog article that expresses this idea.

Seems like if you don’t know exactly what you are building then this method works. With development you have clear criteria of what needs to be done but design can be more subjective. Not every task with the design process results in the same output. Sometimes it is exploration and it is the learnings that are results. Sometimes it is design assets and it is the actual assets that are the results.

How can you apply a single definition of done to such different outputs?

Most of the comments from the blog article didn’t agree with Mike Cohn (the author) but I agree with him.

Advertisements