The Forminators currently use Jira tickets to 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 left’ 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.
What is a 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
Code comments updated and complete
Jira ticket includes link to code repository
Jira ticket requirements, story outline, and conclusion are updated
Story accepted by the PO
Ready for PR discussion (including the NR team collaborators)
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
Confluence