DX PoC readiness checklist
Use this checklist before a first call so the sprint can move quickly and stay focused.
Checklist
A strong PoC starts with evidence, ownership, and a decision path.
- Named owner
- Sample data
- API or export access
- Success metric
- Risk constraints
- Decision after demo
How to use it
Use the checklist before the first scoping call. If several answers are missing, start with a paid audit before promising a build sprint.
- Confirm one business owner
- Collect 5-20 sample records
- List API and export options
- Name the demo audience
- Write the decision after demo
Readiness signals
The best PoC candidates are specific, measurable, and close to real users. Weak candidates sound important but cannot be tested with available data.
- Real workflow pain
- Accessible sample data
- Visible manual step
- Clear user group
- Stakeholder willing to attend demo
Checklist output
- PoC candidate: One narrowed workflow with owner, users, and target decision.
- Data note: Available samples, missing fields, API access, and security constraints.
- Success metric: A measurable proof point such as time saved, acceptance rate, or API success.
- Next step: Audit, PoC, sprint, or pause recommendation.
Preguntas frecuentes
- What if we do not have API access yet?
- You can still start with exports or sample files, but API access should be treated as a sprint risk.
- How much data is enough?
- Enough to represent common cases and a few edge cases. The first sprint does not need a complete data warehouse.