CTO Toolkit
Definition of Ready
A readiness checklist that improves planning quality before implementation begins.
How to use this
Use at refinement. A Definition of Ready is how you paint a picture of what good looks like before work starts — if an item is not ready, improve the work item rather than starting to code and hoping clarity appears mid-sprint.
Problem clarity
- User/business outcome is stated without prescribing the solution
- Scope boundaries and non-goals are explicit
- Dependencies and owning teams are identified
- Acceptance criteria are testable
Technical readiness
- Relevant architecture constraints and standards are linked
- Risks, unknowns and spikes are named
- Data, security and operability concerns are considered
- Sizing is good enough for planning, not false precision
Team readiness
- Someone can start without waiting for a meeting to decode intent
- Reviewers and domain experts are available for the change
- Release/rollout expectations are known if they change the design
This is an original, generic framework for reuse. It is not proprietary employer material.