Toolkit/lens
Definition of Ready (DoR) Checklist
The gatekeeper for sprint entry.
clarityreadinesschecklistinputs
The Definition of Ready (DoR) is the gatekeeper for sprint entry. If you cannot populate these fields in the Lens Wizard, the ticket is blocked. Time is elastic—clarity is not.
🎭Tone:Actionable. Explicit. Evidence-based.
The DoR Wizard Artifacts
In the Governance OS platform, "Ready" is proven by completing the following structural components in the DoR tab:
1. Required Inputs
The raw materials needed before work can begin. E.g., "Market research data" or "Signed API contracts."
2. Cross-Team Dependencies
Hope is not a dependency strategy. Every dependency must be mapped in the Assembler with:
- ☐Named Owner (Who is delivering it?)
- ☐Needed-By Date (When does it block us?)
- ☐Risk if Late (What is the exact impact?)
3. Risks If Started Without
If we skip the inputs, what happens? Documented via:
- ☐Impact Level (High/Medium/Low)
- ☐Likelihood (High/Medium/Low)
- ☐Mitigation Strategy
4. Evidence References
Valid URLs, Jira Ticket IDs, or ADR links proving the DoR is satisfied.
The Null Token Rule
Placeholders (e.g., "TBD", "Link coming soon") instantly invalidate the DoR. A missing evidence token means the scope is mathematically blocked from starting.