Usually I try to get teams to define what 'Done Done' is, but this take kind of spins it on its head in a Brian Eno Oblique Strategy sort of way that I really like:

  1. Untested code isn’t done.
  2. Unreleased code isn’t done.
  3. Undocumented code isn’t done.
  4. Set many, small, specific goals.
  5. Simplicity gives you more options than complexity.
  6. Do something every day. Finish something every week.
  7. One feature finished is better than ten features planned.

Nice and succinct. What's yours?