When is it Done?

Words, they can be hard to come by, misleading (on purpose or mistake) and costly.   The word "Done" means many things to different people during the software development process, with most of them not-really correct or helpful.

• Software Engineer says "it's Done" - The code may have been written but not tested.  Or written but not working, or done "except for some details", or if they told the client it's done, then what does that mean?
• Project manager says "it's Done" - This depends on whom they are saying this to.  Saying this to a client means that they should expect it in their hands NOW.  If it's the CEO then it means, to appease, to inform, to CYA, etc.?
• QA says it's "Done" - Then it means it's clear of bugs, ready to ship?

Done only means "Done" when the client has it in their hands, installed it and it works as promised.  We have all seen or heard to people using the work "Done" to describe, what they perceive as their involvement, in the process of getting a product done.  This word being heard or being used to the wrong person can lead to misleading information (at best) or mistrust (at not best).  I'm sure the stories of shipping blank software to clients to meet a deadline of being done are true (I've seen this in the past).  How is this helpful?

Lets view this from a more lethal point of view and replace the software development context with that of a surgery room and replay the statements.

• The Surgeon was done with the procedure.  Did the surgeon close up, did the staff count the supplies?
• The hospital told the family that the doctor was done.  What does this mean about the outcome?
• The Post-Op recovery was done.  Did the patient wake up?  Is there a complication that will require follow up?

What does this mean for the patient?  The patient only really cares that the everything is completed and there is a successful outcome (they can go on living). 

All involved in the surgery can not and should not assume that because their direct involvement is over that there is a successful outcome.  Only the end result will satisfy the "Done" statement.

So why is the implication, if not the actual word used so much in not the proper context?  Because the same thoughts, fears and feelings are involved in everyone involved.  The boss that does not accept "no" for an answer, the reward / penalty system linked to workers pay that encourages this to the desire to be accepted, impress, etc.  There are a hundreds of ways to renforce behavior that is not beneifitial to others or ourselves.

(These can exists in cycles until the end)
------
Design
Development
QA
-------
Shipping
-------
Installed and Reviewed
Done!