Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This helps our team agree on a standard across our dev community, or UX community. This helps onboard new staff, and also establishes understanding and trust with partners we collaborate with.

...

DRAFT: Definition of Done

Forminator’s Definition of Done (DoD)

To ensure Built-In Quality and an Agile approach to Product Development, Forminator’s DoD consist of:

...

  • Definition of Done (Shippable)

...

  • Definition of Done (Deployed/Released)

...

DONE (Shippable) definition for Development work

...

  • || also known as Done Done

Definition of Done (Shippable)

  1. Code/Content produced (In Progress)

  2. Code tested by the developer || Content reviewed and placed in Confluence by the developer (In Progress → Review)

  3. Code/Content peer reviewed (Review | Peer Review)

    1. Code/Content updated and completed based on comments

...

  1. Code is reviewed by the UX to confirm functional/design requirements are met (Review | UX Review)

    1. Code updated and completed based on comments

  2. Jira ticket includes link to code repository || Jira ticket includes link to the Confluence page for content (Review)

  3. Jira ticket

...

  1. acceptance criteria are met and conclusion

...

  1. is stated/updated in the comment section by tagging Product Owner (Review → Done)

  2. Story accepted by the PO

...

  1. and Ready for

...

  1. Pull Request/Deployment (Done)

Definition of Done (Deployed/Released)

  1. Commit

...

Is reviewed by the PO and (dev. peer where required)

...

Commit time is scheduled

...

Changes are implemented and both code repository and Jira ticket comments are finalized

...

Deployed

DoD for Releasable UX design work:

...

Usability review

...

User feedback

...

Create/Update

...

  1. for Pull Request/Prod Merge followed the DevOps guideline

  2. Code is updated/finalized

  3. Deployed