/
Definition of Ready to Start (DoR) for Epics/Requirements

Definition of Ready to Start (DoR) for Epics/Requirements

Definition of Ready

Definition of Ready (DoR) is not a rigid rulebook but a set of practical guidelines used to determine when an epic or requirement is sufficiently clear and feasible for the development team to begin work. It sets expectations, reduces uncertainty, and enables more predictable delivery. Source Scrum Alliance Scrum Guides

Pre-Requisite

  • Priority is clear and agreed with stakeholders

Proposed Structure of Analysis

  1. Epic/Requirement Summary (clear, concise, value-driven) as per CPS New Requirement, including

    1. Functional requirements

    2. Error scenarios

    3. Performance and Characteristics

  2. Optional: Dependencies (risk, blockers)

  3. Design analysis ready.

    1. Outstanding open issues/unclear items reviewed and documented with Action Point on responsible stakeholder(s)]

  4. Optional: User Story Breakdown and Mapping - high level

Final Gate

(add to the bottom of the main analysis page)

Epic Lead to ‘Check the boxes’

Requirements clear and agreed
Design Analysis completed and reviewed by at least one team member, preferably epic co-lead
No blocking items

 

PS: Error scenarios, performance and characteristics are to remain flexible but must be signed off before delivery of the epic/requirement