Definition of Ready (DoR) β
The described definitions on this page show the focus on guidelines for working with tickets in the onyx team.
A component ticket must fulfil the following aspects to be considered ready:
| Description | UX/UI | DEV | PO |
|---|---|---|---|
| The design is linked | π§βπ¨ | - | π§βπΌ |
| The acceptance criteria are defined => AC has specific steps/interactions defined | - | - | π§βπΌ |
| Dependencies are defined and completed | - | - | π§βπΌ |
| Implementation details are noted | - | π§βπ» | - |
| Comparable implementations are linked | - | π§βπ» | - |
| Matching ARIA patterns are linked, if applicable | π§βπ¨ | π§βπ» | π§βπΌ |
| No open questions and ToDos | π§βπ¨ | π§βπ» | π§βπΌ |
| Ticket was estimated | π§βπ¨ | π§βπ» | π§βπΌ |