Spaces
Apps
Templates
Create
Operational Data Environment
All content
Space settings
Content
Results will update as you type.
ODE
•
ODE Overview
•
ODE Current Sprint
ODE Agile Process
•
ODE Definition of Done
•
ODE Definition of Ready
ODE Product Backlog Items
•
ODE Requirements SOP
ODE Standard Operating Procedures
ODE Engineering
•
ODE Terminology & Dictionary
ODE Archive
ODE Metadata Bug Impact, Resolution, and Prevention
Blogs
Operational Data Environment
/
/
ODE Agile Process
/
ODE Definition of Done
Summarize
ODE Definition of Done
Tamer Morsi (Unlicensed)
Hamid Musavi (Unlicensed)
Owned by
Tamer Morsi (Unlicensed)
Last updated:
Jan 23, 2019
by
Hamid Musavi (Unlicensed)
1 min read
Loading data...
DEFINITION OF DONEÂ Â |Â Â
Good Enough
General
User acceptance criteria in the user story has been met; this includes user acceptance testing
The code has been pushed out to GitHub
This process has been documented in jira & release notes pushed to GitHub
Any discovered Defect(s) are added to Jira
All work-items and related work-items are updated in Jira to reflect their current State/Status
Demonstrated to Product Owner and PO Approval given during the Sprint Demo in order to close the Jira ticket/work-item
PO has approved this Jira ticket/work-item to be worked on during the Sprint (aka. no item can be brought into a Sprint without explicit PO approval)
User-Stories
Acceptance Criteria in the User-Story has been QA's/Tested for functionality
Unit testing has been completed
Â
90%+ Test Code Coverage
The Story's status/state is properly updated in Jira
Any higher level requirements (such as the story's Epic) is updated if necessary
Epics
Defects/Bugs
Spikes
Tasks
Enablers
Sprint Demo Requirements
All Definition of Done have been met
{"serverDuration": 50, "requestCorrelationId": "125ff9f087be4838a2a936e89655d940"}