• Meets Acceptance criteria
  • When there is code, a PR is created and approved
  • It is tested
  • It is approved by Product Owner (Linda, Julie)


ActorActionAction description
Assignee of the PBI
  • The Assignee confirms the PBI meets the Acceptance criteria
The Assignee of the PBI confirms all changes are made in accordance with the acceptance criteria
Engineer
  • The engineer creates a PR when there is code

For a PBI that includes code, a PR will be created. If the PR is approved, it will be merged. 

The status of the PBI is changed in ADO to "In Review" by the assignee of the PBI for the next step.

Product owner / QC person
  • The PO / QC person verifies the PBI

The Product owner or the QC person will test the PBI in the final environment and check that it includes all bullet points added to the acceptance criteria. This is the last step to look for anything that is still missing or is different from what was agreed upon when the PBI was approved.

If the result of the rest is not "OK", PBI will be sent back to the person that the PBI was assigned with the notes to be taken care of.

Product Owner
  • It is approved by Product Owner
The product owner marks the PBI as "Done" in ADO when the PBI has followed the previous steps and passed each of them. 

DoD Flowchart

  • No labels

5 Comments

  1. Anthony Chow

    "It is tested" - could it mean it has gone through QC?

  2. Anthony Chow

    "It is approved by" - how does it relate to the ticket's state transition? E.g., status = ?

  3. Anthony Chow

    "Meets Acceptance criteria" - who is the judge for it?

    1. Anthony Chow

      An example to enhance it could be: "Assignee of the PBI confirms all changes are made in accordance with the acceptance criteria."

  4. Anthony Chow

    Best way to write each bullet point is <<actor>> <<action>> <<action description>>