在當今充滿變數和快節奏的大環境下，一個產品的上市時間已經成為產品成功與否的重要因素。如果對于“完成”沒有一個清晰的定義，那么很可能會遭遇產品延期，風險，并且增加公司成本。

“完成的定義”也被俗稱為DoD，它是一個很有用的工具，可以用來為產品的交付定義各種條件和參數。每個組織根據不同的參數為產品勾勒出不同的DoD。

產品參數可能包括團隊資源，技術水平，剩余時間，客戶的驗收標準等，所有這些參數都是動態的，并且在整個產品生命周期中是可變更的，變更也會帶來完成的重定義。

通過為產品定義明確的標準和參數 ，管理層可以輕松掌握產品進度，如果需要的話還可以根據情況改變DoD。

DoD可以被視為一個可交付產品的檢查清單，也可以被看作是產品的出廠標準。

例如，您可以在所有的單元測試和驗收測試都通過，并且代碼審查和文檔工作也都完成的情況下，才定義一個產品“完成了”。同樣一個產品，完成的定義也可以是該產品沒有任何受阻性缺陷，并且高優先級的缺陷數少于2個。因此，相同的產品可以有兩個不同的完成定義。

最后，DoD可以應用到軟件開發生命周期的各個階段，或者應用到整體產品中，或不同的項目等級中（比如開發Sprint周期，發布等）?？傊?， DoD的明確定義和一致使用，可以引導產品加快上市時間并為產品做出準確估計。

In today’s dynamic and fast paced environment a product’s time to market has become an important factor in a product’s success. With no clear definition of done, it is highly possible that the product suffers from delays, risks and increased company costs. 

‘Definition of Done’ also popularly known as DoD is a useful tool in defining the various conditions and parameters which mark the product as shippable. Every organization outlines a different DoD for their products based on different parameters.

Product parameters may include team resources, skill level, hours remaining, customer’s acceptance criteria, etc. All these parameters are dynamic and can change overtime throughout the product lifecycle which in turn changes the definition of done.

By clearly defining the criteria and parameters for the product, the management can then easily measure the progress of the product and if required can also alter the DoD as the situation demands.

DoD can be treated as product checklist for a shippable product or can also be perceived as the exit criteria for the product.

For example, one could tag the product as done by defining the condition that all unit test and acceptance tests should pass and code review and documentation should be complete. For the same product, the definition of done could also be that the product should not have any blocker bugs and no more than 2 high priority bugs are allowed. Hence, the same product can have two different definitions of done.

Lastly, DoD can be applied to individual phases in the software development lifecycle or can be applied to the product as a whole or at different project levels such as sprints, releases, etc. In summary, with the DoD clearly defined and used with consistency can lead to accelerated time to market and can assist in making accurate estimates for the product.