在当今充满变数和快节奏的大环境下，一个产品的上市时间已经成为产品成功与否的重要因素。如果对于“完成”没有一个清晰的定义，那么很可能会遭遇产品延期，风险，并且增加公司成本。

“完成的定义”也被俗称为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.