At one previous job I was at, people were saying things are done when they weren't. Then the PM started going, is it done-done? Oh sure. I think that mostly

At one previous job I was at, people were saying things are done when they weren't. Then the PM started going, is it done-done? Oh sure. I think that mostly meant "is it actually checked in and running?" Then when we had bugs, they would come around and ask, is it done-done-done (said quickly, with a sense of doom)? I love the "done enough for now.," although I do find some use in breaking down doneness. My levels of done: 1) I've got a prototype or POC that works. I've cracked the hardest issues and gotten it to work, at least in some way. 2) Code is buttoned up, checked in, and running in the build (probably in a branch), maybe even reviewed. 3) Code is tested, and tests pass 4) Code is integrated and working functionally as part of a system. People are able to call it and rely on it. Proves code does what it needs to. So I really try not to say "it's done," but more where it is at in this SDL.