*Planted: March 2025 | Last Tended: 24 April 2025* There are generally two definitions of done during game development production: the [[🌱 Experiential definition of done]] and the functional definition of done. The functional definition of done is usually by default the first thing that needs to be hit and is usually the answer to these questions: - what is needed just to get this feature working in the basic sense? - How functional is functional? - Does everyone on the team have the same shared understanding of what it means for this feature to be functional? - What's the least amount of work that can be done to achieve the definition of "functional"? Functional is often a requirement for other features' [[🌱 Experiential definition of done]] to be properly evaluated -- pieces A, B, and C might need to be functionally done for experience D to be evaluated at some minimum bar. It also provides a shared understanding of the level of feedback needed on this feature to figure out next steps -- while we might acknowledge that experientially the feature is lacking certain criteria, we know by defining the functional definition of done that we're not trying to hit that bar at this step.