Guy kolbis

When you say that you are done with a task, what do you mean?

Does it mean you completed the code?

Does it mean you created tests for that code and all the tests passed?

Does it mean you integrated the code back to the repository and execute a new build?

Does it mean you had your R&D manager review your code?

The point I am trying to explain is that there are so many definition to the term “done”. So I will ask you again: what do you mean when you say done?”.

In my opinion there is “right” answer, nor there is no “single” answer. The term “done” should have it own meaning within your development team. Here is what I usually do: I gather a definition and make sure that everyone agrees with that (according to the company and the situation in hand). Once I have this definition, I make sure everyone in the team knows it, so when I ask: “Is this task done?”, we will all know what is the meaning behind it.

Although there is no single answer or right answer, I strive to make sure that a coding task is (at least):

1. Well coded.
2. Tested.
3. Reviewed.
4. Integrated.

So, you can create a checklist to enforce the term (as above) or you can create a simple rule: “It is done when the tester say so”.

However, there are exceptions, for instance consider the two:

1. Create a new report.
2. Create a manual for the report.

It is clear that you would give different translation to each. My way to solve that is to add another field to a work task, that allows you to define the “done” term.

That’s it, now I am done ;-)