• In green = what we like
  • In blue = what is similar 
  • In red = what we think may not be used


The Definition of Done (DoD) applies for all user stories that the team is working on. In contrast to this, Acceptance Criteria are defined specifically per User Story as required by the Definition of Ready (DoR).

This should clarify how DoR, Acceptance Criteria and DoD relate to each other.



Salesforce team existing stuff

Barbara's propositions

SAFe 6.0 (and more)




DOD (close the sprint)

  1. US has DA approval? (should be part of Technical aspects in DoR )
  2. Dependent ‘has to be finish together’ stories completed
  3. Code Review was done?
  4. Unit Tests passed?
  5. Test class coverage >85% (if code needed)
  6. Development/Configuration deployed into Proj_INT? (local env)
  7. PDS identified and Written into Jira? (but may be too local to CRM teams)
  8. Functional Test scripts written by US?
  9. NRT and Sanity Test scripts identified, if needed created and linked with US. 
  10. All acceptance criteria are passed?
  11. Functional Documentation written
  12. Technical Documentation written
  13. A demo of US was done to the PO?
  14. Product Owner reviewed and accepted?

Definition of Done 

Is a shared understanding within the team of what it means for a user story or task to be complete. A user story is considered "done" when it meets the following criteria:

  • All Acceptance Criteria Met: The user story fulfills all the acceptance criteria outlined in the Definition of Ready.
  • Code Complete: The code has been written, reviewed, and meets the team's coding standards. 
  • Code Reviewed: The code has been peer-reviewed, and identified issues have been resolved.
  • Tested All unit tests, integration tests, and any other relevant tests have been written, executed, and passed.
  • The code should be free of critical bugs. Any other bugs identified are documented
  • Deployed to UAT/INT : The story has been deployed to a staging environment and verified as functioning as expected
  • Documentation Updated: Any necessary documentation, including user documentation, technical documentation, or inline code comments, has been updated.
  • Product Owner: If applicable, the feature has been demonstrated to PO.
  • User Acceptance: If applicable, the feature has been demonstrated to stakeholders.


(For SAFe teams/ to be discussed

DODD (release train)

  1. Final release updated?
  2. Development/Configuration deployed into INT?
  3. No blocking defects in INT?
  4. Deployed to UAT?
  5. US accepted by the Business?
  6. Non-regression tests completed in UAT?
  7. No blocking defects in UAT?


Release level

  • All capabilities done and meet Acceptance Criteria
  • End-to-end integration and solutions V&V (Verification & Validation) done
  • Regression testing done
  • NFRs met
  • No must-fix defects
  • Release documentation complete
  • All standards met
  • Approved by Solution & Release Management