Definition of Done for a User Story

Design Compliance with Mockups (Dev, QA)

Unit tests passed (Dev)

Code reviewed and approved by one person (Dev)

Code Deployed and checked after deployment on stage (Dev)

Acceptance criteria met (Dev, QA, PM, PO)

Product Owner accepts the User Story after QA (only big tasks) (PO)

Documentation: Relevant documentation (user story in confluence) is updated (PO, PM, QA), updated visual design and documented (Designer), and API documentation (Dev).

No Open Defects/Bugs with critical, high, and medium priority (Dev, QA).