...
...
...
...
KPI
...
Completed Jul-Sep 2022
...
Tasks for Oct-Dec 2022
...
(General tasks)
...
Create KPI reporting dashboard
...
Integrator satisfaction
...
Created Integrator Survey
...
Review with Emily to create combined survey?
Emily to send to integrators
Review survey results and identify tasks to improve
...
Acquire FIO Integrations (FIO team) satisfaction
...
No work done
...
Create internal survey
...
FIO Data Services uptime
...
Cataloged services
...
Establish baseline target
Collect monthly data
...
SDK satisfaction
...
Added question to survey
...
Emily to send to integrators
Review survey results and identify tasks to improve
...
SDK feature coverage and time to release
...
Is this a meaningful KPI?
Steering committee wants this KPI
...
Add to Dashboard
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)
Survey
Overall level of difficulty of integration
1 – Very difficult
2 – Difficult
3 – Neutral
4 – Easy
5 – Very easy
Recommended improvements:
...
Budget
Budget | Target | August | Delta |
USD | $8,000 | $8,000 | $0 |
FIO Liquid | $0 | $0 | $0 |
FIO Locked | $0 | $0 | $0 |
KPIs
September highlights
Integration Support
TODO: Need to track
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Devhub
Building a node (Michael): https://developers.fioprotocol.io/docs/chain/node-build
Transaction fee: https://developers.fioprotocol.io/docs/general-functions/get-fee
FIO Development process (Ed): https://developers.fioprotocol.io
...
1 – Poor
2 – Fair
3 – Good
4 – Very good
5 – Excellent
Recommended improvements:
Technical support
1 – Very dissatisfied
2 – Dissatisfied
3 – Unsure
4 – Satisfied
5 – Very satisfied
Recommended improvements:
SDK
1 – Poor
2 – Fair
3 – Good
4 – Very good
5 – Excellent
Recommended improvements:
Integrator satisfaction
...
Question
...
Integrator 1
...
Integrator 2
...
Integrator 2
...
Integration Features (Filled out FIO team)
...
Overall level of difficulty of integration
(1 – Very difficult, 2 – Difficult, 3 – Neutral, 4 – Easy, 5 – Very easy)
...
Documentation
(1 – Poor, 2 – Fair, 3 – Good, 4 – Very good, 5 – Excellent)
...
Technical support
(1 – Very dissatisfied, 2 – Dissatisfied, 3 – Unsure, 4 – Satisfied, 5 – Very satisfied)
...
SDK
(1 – Poor, 2 – Fair, 3 – Good, 4 – Very good, 5 – Excellent)
Questions
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.Bug Bounty program: https://developers.fioprotocol.io/docs/contribute/bounty
...
October focus
Integrator tech support
Devhub - Release 2.8 API documentation
Jira Legacy server System JIRA serverId 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d key ISUP-30