Differences

This shows you the differences between two versions of the page.

--- what_does_it_mean_to_be_done [2018/08/27 13:11] – [Process] hpsamios
+++ what_does_it_mean_to_be_done [2018/08/27 13:14] – [Want to Know More?] hpsamios
@@ Line 57: / Line 57: @@
   * Code is complete:
-    * Build and package changes are communicated to build master (e.g., when introducing a new file)
+      * Build and package changes are communicated to build master (e.g., when introducing a new file)
-    * Code meets product coding standards
+      * Code meets product coding standards
-    * Code has been run through static and/or dynamic analysis tools (e.g., Coverity)
+      * Code has been run through static and/or dynamic analysis tools (e.g., Coverity)
-    * Code is checked into source control (with developer and peer reviewer names recorded)
+      * Code is checked into source control (with developer and peer reviewer names recorded)
-    * Internationalization considerations have been met
+      * Internationalization considerations have been met
-    * Internal and external documentation is updated with applicable support information included such as help files and public APIs
+      * Internal and external documentation is updated with applicable support information included such as help files and public APIs
-    * Code is integrated with the main trunk (if not already done)
+      * Code is integrated with the main trunk (if not already done)
-    * Code (or other deliverables) has been peer reviewed (e.g., pair programming counts as peer review)
+      * Code (or other deliverables) has been peer reviewed (e.g., pair programming counts as peer review)
   * Code meets quality standards
-    * Test plans are in place for: Unit, Function, GUI
+      * Test plans are in place for: Unit, Function, GUI
-    * Test plans have been run and passed and (hopefully) automated
+      * Test plans have been run and passed and (hopefully) automated
-    * Test plans are in place for the '-ilities' including performance, stress, load, security, etc
+      * Test plans are in place for the '-ilities' including performance, stress, load, security, etc
   * No new defects
   * End-user documentation is complete
-    * Internal and external documentation is updated with applicable support information included such as help files and public APIs
+      * Internal and external documentation is updated with applicable support information included such as help files and public APIs
   * "Conditions of Satisfaction" or "acceptance criteria" have been met
-    * Some organizations also add in "Product Owner has accepted the story" as part of this thinking
+      * Some organizations also add in "Product Owner has accepted the story" as part of this thinking
   * Item statuses in related tracking systems (Jira, Siebel, etc.) have been updated
+====== Want to Know More? ======
+  * [[:how_do_we_initially_setup_our_definition_of_done|How Do We Initially Setup Our Definition of Done]]
 {{tag>Consultant Tools DefinitionOfDone DoD FirstSprint FAQ}}
-~~LINKBACK~~
-~~DISCUSSION~~