My problem with this type of argument/technique is they constantly identify a completion state. Stop thinking about completion, and start thinking about milest

My problem with this type of argument/technique is they constantly identify a completion state. Stop thinking about completion, and start thinking about milestones (waypoints, checkpoints, revisions, whatever). A popular startup mantra is release early and often; another popular startup technique is to release unfinished. I say we need to stop thinking about what's been done, and also stop thinking about what needs to be accomplished before we are finished. Think about what needs to be completed for the next checkpoint. In the ever-popular race metaphor: Put your right foot in front of your left, then put your left foot in front of your right. Congratulations, you made it one step further. Tell everyone what you accomplished, then take the next step. Using this concept, the hard part becomes determining what exactly constitutes a step. This is no small task, but it seems easier to deal with than constant concern about 'finishing'.