KPI | Completed Jul-Sep 2022 | Tasks for Oct-Dec 2022 |
|---|---|---|
(General tasks) |
| |
Integrator satisfaction |
|
|
Acquire FIO Integrations (FIO team) satisfaction |
|
|
FIO Data Services uptime |
|
|
SDK satisfaction |
|
|
SDK feature coverage and time to release | Is this a meaningful KPI?
|
|
Integrator satisfaction (based on post-integration survey)
Acquire FIO Integrations (FIO team) satisfaction
FIO Data Services uptime SLA
SDK time to integration of new features (after release to chain)
A. Overall level of difficulty of integration
(1 – Very difficult, 2 – Difficult , 3 – Neutral, 4 – Easy, 5 – Very easy)
Recommended improvements:
B. Documentation (https://developers.fioprotocol.io)
(1 – Poor, 2 – Fair, 3 – Good, 4 – Very good, 5 – Excellent)
Recommended improvements:
C. Technical support
(1 – Very dissatisfied, 2 – Dissatisfied, 3 – Unsure, 4 – Satisfied, 5 – Very satisfied)
Recommended improvements:
D. SDK / Libraries
(1 – Poor, 2 – Fair, 3 – Good, 4 – Very good, 5 – Excellent)
Recommended improvements:
Would it make sense to remove this WP and move the budget and resources into the Partner Success and Core Chain WPs?
Does the steering committee think it is important to track this project and cares about the KPIs?
Technical support and QA for partners is done in the Partner Success WP
Partners require support for their API nodes which is in the Core Chain WP
Both the API and SDKs (and the associated documentation) are used by integrators. So, why have them in separate groups?
SDK features are closely tied to API features.
6/23/22 Steering committee meeting - Decision made to keep this as a separate WP for now.
Other KPIs that would be helpful
6/23/22 Steering committee meeting - No additional KPIs suggested.