The Definition of Done (DoD) represents our team's formal definition of quality for all Product Backlog Items (PBIs). Definition of Done (DoD) is crucial to a highly functioning Agile team. DoD is a checklist/process that the team must perform/complete successfully before declaring the work to be potentially shippable.
The Forminators currently use Jira tickets to visualize, manage, and track story progress from assignment to complete. Final completion is measured as
by working software, committed code in the production instance of Forms.io
by UX design, having human design elements accepted and working
For Proof of Concepts, for Explorative research (Splunking) and for DevOps documentation “How do i?” guidance the definition is a little trickier. It depends. To that end we shall be working to clearly define DoD for our team to adhere to - and to ensure we ‘shift let’ and build quality and pride into our completed work.
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.
...
...
Forminator’s Definition of Done
...
Essentially a pre release checklist of all tasks that the assignee must complete. Meeting the definition of done ensures we meet quality, and that we ensure consistency.
Our in-flight DoD work is currently shown below. Look for updates as our team practices mature
DoD for Development work:
DONE (shippable)
...
Code produced
...
Code tested
...
Code peer reviewed
...
(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) || also known as Done Done
Definition of Done (Shippable)
Code/Content produced (In Progress)
Code tested by the developer || Content reviewed and placed in Confluence by the developer (In Progress → Review)
Code/Content peer reviewed (Review | Peer Review)
Code/Content updated and completed based on comments
Code is reviewed by the UX to confirm functional/design requirements are met (Review | UX Review)
Code updated and completed based on comments
Jira ticket includes link to code repository || Jira ticket includes link to the Confluence page for content (Review)
Jira ticket
...
acceptance criteria are met and conclusion
...
is stated/updated in the comment section by tagging Product Owner (Review → Done)
Story accepted by the PO
...
and Ready for
...
DONE (released)
Commit request is reviewed by the repository maintainer/gatekeeper
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
Pull Request/Deployment (Done)
Definition of Done (Deployed/Released)
Commit for Pull Request/Prod Merge followed the DevOps guideline
Code is updated/finalized
Deployed
Definition of Done (Released: UX/Service Design)
Usability Review/User Feedback
Create/Update Confluence