# Definition of Ready (DoR) & Definition of Done (DoD)
# Definition of Ready
The DoR describes the requirements, before a developer can start working on a task.
# Definition of Done
The DoD describes the requirements which are needed to complete a task.
# Change Request (CR) / Feature Request (FR)
# DoR
- Ticket is prioritized (approved by PM)
- Estimation is done (T-Shirt sizes / person days)
- Team understands requirements and has a rough idea of how to implement
- Linked Issues (related to)
- Linked to an Epic (if existing)
- Mandatory fields are filled
- Story describes the problem, not the solution
- Acceptance criteria are added
- Deviating NFRs [1] are defined
# DoD
- Acceptance criteria are fulfilled / measured / automatic
- NFRs are fulfilled / measured / automatic
- Documentation has been done
- Time-logging has been done
- Approval-link and Docu-link are available
- Software is in production/live
# Incident
# DoR
- Ticket has been prioritized (approved by 1st Level Support)
- Ticket has been assigned to a team (by 1st Level Support)
- Before starting, make sure you understood the problem
- Other issues have been linked (related to, route cause)
- Mandatory fields have been filled
# DoD
- Automated tests are in place which makes sure this incident cannot happen again [2]
- Business critical processes / features are added to PRTG [3]
- Time-logging is done
- Fix is in production/live
- Documentation is done
- Standard NFRs [1:1] and special NFRs are fulfilled