DOD and Dor, two artifacts to reduce "cognitive bias"

In Agile Development , Let all members keep the same goal 、 It is very important to keep pace with the rhythm , But in teamwork , Cognitive bias is inevitable . Demand flows in different links , Is there any way to ensure that all members have the same understanding , Minimize deviations ？

Today I want to introduce agile development , Two artifact of consensus building ：DoR and DoD.

One 、 DoR What is it? ？

DoR = Definition of Ready, to 「 Be ready 」 The definition of , It is the first door to control the quality of R & D in agile development .DoR Pay attention to the quality of the starting point of R & D , It defines the minimum requirements that user stories can be accepted by the R & D team and enter the development stage , It is the standard of demand access .

DoR The value of is , It standardizes the quality bottom line of development objects , It can effectively prevent resources on the development side 、 A waste of time or energy ： If a user story to be developed does not match DoR requirement , Then the R & D team has the right to return it , Don't develop it in recent iterations .

01 Garbage In, Garbage Out

quote Brian Will Point of view ：“ A user story 「 Be ready 」 It's very important —— There will be problems in putting incomplete or unoptimized user stories into the sprint , Because it will follow 「Garbage In, Garbage Out」 principle ： If developers are dealing with user stories that are not detailed enough or poorly defined , They will not produce high-quality code .”

Brian Think a 「 Ready Ready」 To do items should be clear 、 Feasible and testable .

• Clear （Clear） It means that all members of the team can reach a common understanding of the same user story . Write user stories through collaboration , And add acceptance criteria for high priority , The clarity of requirements can be improved .
• feasible （Feasible） Require user stories to follow DoD Be completed in a sprint , otherwise , The story needs to be further decomposed .
• Testable （Testable） It means that a user story can use some method to determine whether it works as expected . Acceptance criteria ensure that every story is testable .

02 DoR For reference

• User stories match INVEST principle
• User stories are clear
• User stories are testable
• User stories are feasible
• User stories have been defined
• User story acceptance criteria have been defined
• User story dependency is clear
• User stories have been granular by the development team
• Scrum The team has accepted UI Prototype design
• The performance indicators of the specified scenario are clear
• The scalability index of the specified scenario is clear
• The safety indicators of the specified scenario have been clarified
• The person who accepts the user story is clear
• The team knows what the user story means

Two 、 DoD What is it? ？

DoR Pay attention to user stories to be developed , and DoD Focus more on the value increment to be released .

DoD = Definition of Done, Complete the definition , It is the second door for controlling the quality of R & D . it It is the standard of demand approval , Usually presented as a short document in the form of a list , User stories are defined as 「 complete 」 The minimum acceptance conditions required , Often by the person in charge of the product PO Negotiate with the development team to decide .

DoD By establishing common standards , Ensure that every member of the team has the same understanding of the completion of value increment , Avoid potential cognitive bias inside and outside the team ; meanwhile , The contents of the list can also improve the information transparency of the team , Assist in the evaluation and planning of work points , Promote the completion of the story .

01 DoD Content scope of

In Agile Development ,「 complete 」 signify 「 No more work is needed , Direct delivery 」, therefore DoD The content should at least cover the design 、 code 、 Integrate 、 A complete set of product development processes such as testing and recording . Brian Will Pointed out that DoD The following is usually explained ：

• The operating environment and integration level of the user story （ Which specific version Linux、Android、iOS Or browser ）？
• What level of documents need to be output （ Automatically generated Javadoc, Or the complete end user manual ）？
• What are the quality expectations （ Basic functions for demonstration , Or a fully functional and robust application ）？
• What are the safety expectations （ No safety review is required , Still need from code review 、 All aspects from code scanning to network security configuration should be subject to Security Review ）？
• What are the scalability expectations （ For demonstration 10 concurrent , Or expand to 10 Million concurrent users ）？

02 DoD Different dimensions of

Scrum The alliance is based on different levels of demand , take DoD There are three levels ： A user story DoD、 sprint DoD And release DoD.

A user story DoD, Also called function / demand DoD. It states the bottom line of story deliverability , That is, what should be done in the user story before it can be judged as the completion of development , Meet deliverable Standards . A user story DoD The formulation of can be considered from the following two aspects ：

• The description and disassembly of user stories conform to INVEST;
• User stories have acceptance criteria , namely Acceptance Criteria.

sprint DoD, Or iterations DoD, Define each Sprint What needs to be done , Its output is deliverable . It usually includes the following ：

• All code passes static detection , Serious problems have been corrected ;
• All new codes have been Code Review;
• All completed user stories passed the test ;
• All completed user stories get PO Validation of the .

Release DoD Defines the minimum requirements for incremental delivery , You can refer to the following contents to assist in formulating .

• Requirements required to complete the release plan ;
• Complete at least one full regression test ;
• Meet quality standards (Quality Gate), For example, all grades are 1、2 All defects have been repaired ,3、4 Class defects do not exceed 10 individual ;
• There is a release notice , namely Release Notes;
• There is a user manual ;
• All product related documents have been updated ;
• The code has been deployed to the publisher , And smoke through ;
• The original requirement submitter completes UAT;
• Operation and maintenance 、 market 、 The new function training of customer service has been completed .

Besides , At the subtask level , Agile teams can also use Development tasks DoD Better standardize the completion of tasks , such as ：

• The code has been submitted to Git;
• The code passed unit tests ;
• The code through Code Review;
• The code passed the integration test .

03 DoD For reference

• The code is complete （ All the to-do items have been coded ）
• Code commented 、 Has been submitted , The current version of the version library can work normally
• Pairing view is complete （ Or use pair programming ）, The code conforms to the development standards
• Build without errors
• All unit tests passed
• Deploy to the test environment and pass the system test
• adopt UAT（ User acceptance test ） And sign to confirm that it meets the requirements
• Any compilation / Deploy / Configuration changes have been implemented / Record / communicate
• The related documents / The chart has been completed or updated
• The remaining hours of the task have been set to 0, Task closed

3、 ... and 、 Liga summary

1. DoR Control the starting point of R & D , It is the standard of demand access . User stories must meet the requirements of the team to enter the list to be developed .
2. DoD Control the end point of R & D , It is the standard of demand approval . It defines the minimum acceptance conditions for incremental value delivery , Applicable to all user stories .
3. Garbage in, garbage out. Agile teams must strictly control the standards of demand access , In order to promote the follow-up work more smoothly , Ensure R & D quality .

Reference material

1. https://resources.scrumalliance.org/Article/definition-dod
2. https://www.linkedin.com/pulse/definition-ready-dor-vs-done-dod-brian-will

---

Learn more about agile development 、 project management 、 Industry trends and other news , Pay attention to our [email protected]  Or click on LigaAI - A new generation of intelligent R & D cooperation platform , Apply online to experience our products .