Definition of ready DOR and definition of done DOD templates

Defining when a task can be started or when the task is completed is a basic activity that helps the development team to control the flow of tasks and avoid getting stuck when requirements are not clearly defined. It also prevents sending uncompleted changes into the development branch

Definition of ready DOR

First definition helps the team to validate if a task is ready for starting the development. Next is a basic list of validations than can help the team determining if a task has the necessary information:

├── Is ready to start?
│   └── acceptance criteria is correctly described?
│       ├── If is a user interface, are the prototypes well defined and the gherkins written?
│       ├── If is an API, are all the entities and their attributes defined?
│       └── if (task cannot be started)
│          ├── add a comment
│          ├── move to parking lot
│          ├── assign to the person responsible for solving
│          └── end
├── update task status
│   ├── check estimated story points
│   ├── move the task to in progress
│   ├── create branch to work
│   └── create a pull request
└── end

Definition of done DOD

├── basic validation
│   ├── follows TDD required structure?
│   ├── do structure follows CQRS structure?
│   ├── were all requirements completed?
│   ├── follows the required graphical design?
│   ├── are transactions tracked in AI?
│   └── are resources translated?
│       └── was static code analysis performed?
├── before sending a pull request
│   ├── validate that all automated tests are working
│   ├── static code analysis passing
│   ├── format code if needed
│   ├── check comments grammar
│   ├── remove any commented code
│   └── remove visual studio warnings
├── developer test environment validation
│   ├── commit changes
│   ├── merge changes from the integration branch
│   └── send pull request