Skip to content

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:

  1. Acceptance criteria
  2. Non-functional requirements
  3. Estimate in story points
  4. 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.
Clone this wiki locally