Just because you did, doesn't mean it's Done

Trying to be Agile is a constant learning experience, you even have to coach yourself, and I had never thought that the kitchen would give me such a big reminder. In my household, we try to speak Agile as a constant refresher (there is no do...be, right?), and in passing I told my husband that I had cleaned the kitchen, and he stopped dead in his tracks. I thought to myself "Rookie move, Sam", because I knew what was coming. My husband said, "Did you really? Is it actually Done?", and I knew that he was talking about the lovely Definition of Done. It truly got me thinking, as I had previously and hastily taken down the acceptance criteria for the kitchen being clean, but I didn't really think about what Done meant in regards to my kitchen. So, instead of pondering this, I made a handy dandy User Story Map for the Definition of Done.

If you look at the map, I refer to myself as the "Keeper of the Household", or "KOH", I could have easily put "User", but I like to maintain that I am not the only one in my home that uses the kitchen, whether between making lunches, breakfasts, and most of the time dinners, cleaning, etc., makes me feel like I am. I have also included all of the acceptance criteria in the form of a User Story.

I know that this is a bit of a short blog, but I feel that it should be brought to attention that done isn't Done, until all of the criteria is met. So the kitchen being "Done", with me being Agile me, means that all of the acceptance criteria has been met within the tasks. I have mapped out the entire criteria that means that the kitchen is Done with a capital D, and now, when I tell my husband that the kitchen is Done, we will both know what it means!