Versions Compared

Old Version 5

changes.mady.by.user George Worrell

Saved on

compared with

New Version 6

changes.mady.by.user George Worrell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Objective (DRAFT)

To maintain the existing implementation and construct new features to support adoption and use of the FIO dashboard for end users as well as integration partners.

...

The mission of the dashboard is to drive adoption by end users and integration partners with the net effect being increased use of FIO handles and domains which create direct paths to revenue for the organization as well as defining FIO as THE protocol of choice within multiple industry sectors.

Strategy

TBD ..

Use Cases

End User Segments (P2P)

...

  1. Strategic

    1. Roadmap Feature Specs

    2. Resource Planning

    3. Development Feature Scope

    4. Marketing Planning

    5. Educational Planning

    6. Metric Planning

  2. Tactical Implementation

    1. UX

      1. Current Roadmap

      2. QA

      3. Bug Fixes

    2. Development

      1. Current Roadmap

      2. QA

      3. Bug Fixes

    3. Marketing

    4. Educational

      5. Metrics

  3. Ongoing

    1. Steering Committee Working Sessions and Reporting

Future

  1. Strategic

    1. Product Refinement Plan (based on metrics)

    2. Future Feature Roadmap Ideation and Creation

    3. Resource Planning

    4. Follow-on Marketing

    5. Continual Metric Review

  2. Tactical Implementation

    1. Existing UX Tweaks

    2. New UX

    3. New Development

    4. New Marketing Campaign

    5. Educational based on new features

  3. Marketing

  4. Educational

  5. Metrics

  6. Ongoing

    1. Steering Committee Working Sessions and Reporting

KPIs

What do you consider success and failure of the worker proposal (details, a statement, a stake in the ground) - Quarterly - Define failure and raging success - Not sufficient to just be a bucket .. To be a KPI for the dashboard, they must be actionable and measurable. Their success depends on objective, statement of detail and the stake in the ground. The following is a proposed schedule and topics for creation of initial KPIs.

  1. Schedule

    1. Q3 2022

      1. Create Initial KPIs

      2. Initial Measurement

    2. Q4 2022

      1. Measurement - TBD

      2. Refinement - TBD

    3. Q1 2023

      1. Measurement - TBD

      2. Refinement - TBD

    4. Q2 2023

      1. Measurement - TBD

      2. Refinement - TBD

  2. Topics

    1. Operational

      1. Uptime SLA

      2. Bug

    2. Success Measurement

      1. Handles

      2. Domains

      3. Use

    3. Roadmap Achievement

Budget

Roadmap

Resource Allocation

It requires the following resources regardless of where it lives structurally:

  1. Director / WP Leader

  2. Strategy

    1. CTO

    / Strategy

    2. CPO

    / Strategy

  3. Core

    1. Lead Architect

    2. Senior Engineer

  4. Implementation

    1. Development

      1. Architect

      2. Engineer(s)

      3. QA

      4. Project Mgmt

      5. Release Mgmt

      6. Ops

    2. UX

      1. Research

      2. Jr. UX Visual/IA

  5. Business ?

  6. Marketing ?