Definition of Ready — Assessment
Evaluate whether a project or sprint is ready for development. Answer each criterion, attach evidence where useful, and submit. A score out of 10 is computed and a recap is sent to Slack. Ready threshold: 8.0.
Project info
Project conditions
AI design skips the UI/UX criterion.
Readiness criteria
1. Business goal & scope
Project objective and in/out-of-scope are clearly defined.
2. Target users / personas
The end users and their personas are identified.
3. Detailed functional requirements
User stories / feature list are documented in enough detail.
4. Acceptance criteria per feature
Each feature has clear acceptance criteria.
5. EPIC / feature prioritization & module sequencing
Epics and features are prioritized; the build order of modules is known.
6. UI/UX design ready
Design deliverables are complete enough to build from.
7. High-complexity features understood by PM/BA
For complex features, PM/BA fully understand and have clarified them.
8. Third-party parties identified & agreed by PM
PM has specified which third parties will be used and the team agreed.
9. Assets, content & access ready
Logo, project docs, and third-party accounts are available/accessible.
10. No remaining project blind spots
Any blind spots you are worried about? If yes, comment below.
Live score
0.00 / 10
Not ready — need ≥ 8.0