M4 - Real services and data
From @Brittany Wolff : I have this Confluence doc and this miro board that detail the (more or less) current state of the usage dashboards. It is built on a series of materialized views which are not in Snowflake, but could probably be recreated there. Except it looks like we don't have teachings in Snowflake yet which is one of the base tables. You can find the SQL for the materialized views in the repo (db/views). I think the current versions would be:
M2 - Legacy platform — dev
Opt-in banner/workflow, user opt-in setting, and global nav changes (§4.5) built on the legacy platform.
M4 - Audit resolution
Every Audit-flagged item (Classrooms/Assignments, Assign, Profile → Recent Activity/History, Release Notes) has a real-vs-faked determination and a decision recorded against §11.
M5 - Legacy platform — QA
QA and regression complete on the §4.5 legacy platform changes; no open blocking defects.
M6 - Full-coverage testing
Unit, integration, E2E, accessibility, performance, and regression coverage per §6 complete across rad-helix and rad-platform-layer.
M7 - Legacy platform — release
Opt-in banner, user setting, and nav changes shipped to production ahead of go-live.
M8 - Full capability parity / go-live readiness
All P1 must-haves at Built; go/no-go checkpoint for Aug 30 launch.
M9 - Phase 1 launch — teacher opt-in live
LIMITED - teacher opt-in testing available; capability to activate for a small subset of users the same day.
M10 - Phase 1 iteration window
Refinements and fixes shipped based on telemetry, Pulse feedback, and further QA from the initial opt-in cohort.
M11 - Phase 2 expansion
Opt-in expanded to the Phase 2 cap
M12 - Phase 2 iteration window
Refinements and fixes shipped based on Phase 2 cohort feedback and QA.
M13 - Phase 3 expansion
Opt-in expanded to the Phase 3 cap; scale/performance validation per §6 confirmed ahead of the 20x jump.
M14 - Phase 3 iteration window
Refinements and fixes shipped based on Phase 3 cohort feedback and QA.
M15 - Phase 4 expansion
Opt-in expanded to the Phase 4 cap — final expansion within this plan's window.
M5 - Adoption and communication
Tentatively use in Q4 to complement PI Planning (led by @Nikkita Willis). Dates TBD.
ContentBot - generated AI metadata
Full AI-forward content architecture for generating standards alignment, grades, subjects, lexile scores and more via extracted text and supporting models, architecture, services, and more. Round one of indexing completed.
Connect to Internal Tools (ScholarBot)
Build to spec in rad layers
@Derek Stutts is building in separate project repository
Testable app (for internal feedback)
Overall functionality accounted for, though may shift with feedback from team and cross-team.
Decision on API Framework
Now (foundation)
8-week workout plan, weekly plan view, AI coach with pre/post-activity and opening-day flows, activity generation, progress tracking and badges, DE asset + standards search, assignments (including public student links). Auth via DE SSO (toggle) behind a passcode gate.
Next
Deepen admin/coach analytics; richer personalization of the coaching path based on teacher profile and prior responses; broaden content/standards integration.
M1 - Initial POC Scaffolding & Data Exploration
Create scaffolding for initial POC and look into fetching data from snowflake. Result is here:
https://rad-mystery-customer-admin.discoveryeducation.com/
M2 - Initiatives Inclusion
Include initiatives and capx budget codes heirarchy per @Nikkita Willis and @Travis Barrs
Later
Full DE SSO rollout (remove passcode gate), expanded grade-band theming, scale beyond pilot cohorts.
M2 - POC Prototype
Based on designs and documentation here:
https://discoveryed.atlassian.net/wiki/spaces/MS1/pages/4739268626/Admin+Dashboard+Prototyping+and+Testing
Will overwrite previous POC and be located here: https://rad-mystery-customer-admin.discoveryeducation.com/
USER MUST BE ON VPN TO ACCESS (for internal testing ... we'll remove this once customers are accessing for testing : )
M3 - Feedback Redesign
Complete design overhaul to stay attuned to evolving project reqs.
M4 - Shift to production timeline
Leverage this work to shift to a production timeline and go-to-market strategy
M4 - Jira Integration
Integration of JIRA epics at the project level. First pass. More to come.
M1 - Roadmap Initial Release
Created v1 in 2 days for internal feedback and communications.
M1 - Kickoff and Scope Lock
M3 - Team Review Mystery Customer Admin with Team
Review Mystery Customer Admin with Team, make any adjustments needed iteratively.