<p>While Scrum is easy in theory and hard in practice, I wanted to hear your definition of Done; i.e. what are the gates (unit test, code coverage > 80%, code reviews, load tests, perf.test, functional tests, etc.) your product has to go through before you can label the product "Done"</p>

There are three nice articles by
Mitch Lacey
,
Dhaval Panchal
and
Mayank Gupta
on this on the ScrumAlliance website.
EDIT:
Basically the whole point is that
done is defined on a project-by-project basis by the team
. The basic need is to agree on the definition, not what the definition is.