Toolkit/lens
Decision Record (ADR)
Template for documenting architectural or scope trade-offs.
decisionsarchitectureaudit
The Definition of Ready (DoR) is the gatekeeper for sprint entry. If you cannot answer these questions with documented evidence, the project is not ready to start.
Tone:Actionable. Binary. Evidence-based.
The 6 Axes of Readiness
Before a project is allowed to enter the Accelerator, it must be scored across six dimensions. Each dimension requires a Valid Reference Link (an Evidence Token).
1. Feasibility (F)
- Architecture reviewed and approved.
- Technical constraints identified.
- No unproven core technologies.
2. Behavior / Operability (B)
- UX/UI designs or API contracts locked.
- Error states and edge cases defined.
- Support/Ops handover path clear.
3. Value Clarity (V)
- Business outcome explicitly stated.
- Success signals defined (measurable).
- Sponsor signed off on the 'Why'.
4. Dependency Volatility (D)
- All cross-team dependencies logged.
- External APIs/Vendors confirmed ready.
- Drop-dead dates agreed upon.
5. Regulatory / Blast Radius (R)
- Compliance/Security review complete.
- Data privacy constraints mapped.
- Rollback plan exists.
6. Novelty / Boundary Risk (N)
- Domain boundaries respected.
- Reuse vs. Build decision documented.
- No 'Shadow Concepts' introduced.
The Null Token Rule
Placeholders (e.g., "TBD", "Link coming soon", or linking to a blank Confluence page) instantly invalidate the token. A missing token means the scope is mathematically blocked from starting.