Mission
The Reporting and Visualization Work Group is being established to evaluate the needs of the community around reporting and visualization and propose a plan to offer a free toolset – that “lights up” the data standard, as part of Ed-Fi Core, that puts the Alliance resources to the most effective use. The mission of the RVWG is twofold: - Identify the classroom use cases for a reporting and visualization offering with the biggest impact on instructional outcomes.
- Provide to the Ed-Fi Alliance a roadmap for the proposed Ed-Fi Core Reporting and Visualization solution.
Goals
The initial focus of the RVWG in reporting and visualization is to: Phase I - Information Gathering - Create a framework to capture and analyze reporting needs of schools, districts, and other LEAs, to solicit feedback on existing solutions and limitations.
- Create use cases based on the feedback captured that can be used to create reporting and visualization solutions that support instructional improvement by teachers and their support staff.
- Propose a prioritized set of 1-2 use cases for implementation, release and maintenance as part of Ed-Fi Core (free offering) with the most significant impact on instructional outcomes.
Phase II - Priority Case Solution Proposasl Based on the approved priority Use Cases: - Develop a common glossary for calculations/metrics used around relevant information to report and options to present that information to users,
- Develop a set of requirements, screen layouts and definitions of calculations/metrics for the prioritized set of use cases.
- Develop a comprehensive proposed plan/roadmap of each use case for governance review and approval including:
- Asset deprecation plan: If group decides to retire Ed-Fi dashboards and create a new reporting and visualization options. This plan should include Impact/Gap Analysis for current users to evaluate the cost/benefit of moving away from their Ed-Fi dashboards implementation to the new offering.
- Upgrade path: If group decides to continue with the current codebase and modify it. Proposal should include upgrade path considerations. (if current assets)
- Technology stack
- Cost considerations
|