-
Notifications
You must be signed in to change notification settings - Fork 3
Definition of ready
Josh Liberty edited this page Feb 25, 2022
·
4 revisions
Before ticket is ready to be taken up for development, the following details should exist:
- Acceptance criteria
- Non-functional requirements
- Estimate in story points
- Technical design:
4.1 For APIs, the contract has been defined. This includes endpoints, payloads, and authentication.
4.2 For tickets requiring communication with an external system, the interface should be defined. A sequence diagram should be provided.
4.3 Database schemas, if applicable.
4.4 Behaviour in various expected error scenarios.
4.5 Recovery behaviour in case of interrupted execution.