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:
- Untested code isn’t done.
- Unreleased code isn’t done.
- Undocumented code isn’t done.
- Set many, small, specific goals.
- Simplicity gives you more options than complexity.
- Do something every day. Finish something every week.
- One feature finished is better than ten features planned.
Nice and succinct. What's yours?