Product Roadmapping

From the Product Vision to the Product Roadmap

This roadmap adheres to the vision articulated on the Project Impact on OHS page. The purpose of the roadmap is to define at a high level the product increments that will bring that vision to life. The roadmap tells stakeholders what the intended outcomes of each increment are and how we will prove that those outcomes have been met. The roadmap also tells the team where to focus their efforts with respect to user research, design, and development.

Product Vision and North Star Metric

Product Vision
The product vision is to build a solution that will greatly improve transparency and oversight so leaders can ensure that TTA is responsive to grantee needs, meets expectations for continuous quality improvement, and produces strong child, family, and program outcomes.
North Star
Our proposed North Star is the TTA Smart Hub as the source of truth for all things TTA: The TTA Smart Hub will make TTA activities highly visible and knowable to all TTA team members and leadership so that the information can be used to make decisions that positively impact TTA responsiveness to grantee needs and enable them to continuously improve the program.
North Star Metric
Over time, the count of trends in TTA activities that are visualized in the Smart Hub will increase and the meaningful implementation of that information will also increase. Initially (in the MVP) will simply start tracking the number of ways we visualize data to enable meaningful decision making based on it. Thereafter, we will look for ways to capture how the data was used.

MVP Version 1.0

MVP Scope

MVP Outcomes and Metrics

MVP Outcome	MVP Metric	Dimension	Comments	Status
TTA Specialists use fewer tools outside of the Hub when reporting on activities, which contributes to making the TTA reporting process more visible to TTA team members and leadership.	How many reports move from Submitted to Approved without passing through the Revisions Requested status? Reports bypassing this status are, we assume, being reviewed outside of the system in emails, MS Word, etc. Reports that hit this status are necessarily being managed more in the Hub. Additionally, how many reports include comments by managers in which they specify revisions requested?	Efficiency	In the wake of the MVP go live, we will deploy a qualitative survey and do usability testing to gather evidence as to how the system has changed what they have to do for reporting. In addition, we will include a capability in the MVP to track user session time in activity reports and we will monitor it to see if it declines over time. The results will be more meaningful once we implement the activity planning features because they will (we anticipate) be used to prepopulate the post-activity reports, thereby speeding up the post-activity reporting process.	Reviewed with PO. Pretty firm at this point.
Program Specialists can easily find a given TTA activity in the system and understand the gist of what happened at it, the goals of the activity, topics that were discussed, the people who attended/participated, the resources that were used, and which objectives were met and which weren't.	We'll do usability testing to measure the ease of finding a specific activity and viewing a summary view. In addition, we'll track the adoption of the feature we build to provide this view by tracking the weekly or monthly active users and then the percentage of those who are Program Specialists and use the feature. (We will review this metric for viability once the user research and design start to give more shape to the prospective feature.)	Transparency	Product Owner noted that Program Specialists will get alerts from other systems that something is up with a grantee and they will then come to our product to investigate the activities completed with that grantee. In the long term, our product may incorporate these alerts, but not in the MVP. The metric hasn't been discussed yet.
Program Specialists can easily find which topics were discussed at activities within their region and see trends such as which topics are associated with objectives that were met vs. objectives that weren't met.	We'll do usability testing to measure the ease of finding and viewing this data. In addition, we can set up a feature adoption metric similar to the one proposed for the preceding outcome.	Transparency		Reviewed with PO. May need one more round.
TTA leaders in the Central Office can track usage of National Center and other resources across multiple regions	Since CO users will be relatively few in number, we can measure this outcome initially with usability testing. To track it over time, we can calculate roughly how long we think it should take a CO user to accomplish the task of tracking resources (or other data of interest to them) and then track the number of CO users spending that amount of time in the product.	Transparency		This outcome is a candidate for moving out past the MVP. The MVP will include the ability to review resources but the target users are specialists and their managers, not the CO.

MVP Scope: Inclusions and Exclusions

Our basic rules for deciding MVP scope:

We will not deliberately include capabilities or business rules found in the old HSES TTA application. We will review it to understand OHS needs; but for product scoping decisions we will rely on user research (both the recent work of 18F and the upcoming work of Ad Hoc).
We will include capabilities and business rules deriving from the 18F-built SmartSheet, because it's the first product roll-out based on user research. If we exclude any SmartSheet capabilities, it will be because
- we've validated that they're not wanted or not wanted in their current form or
- if they are wanted, we've negotiated with stakeholders to release them at a later time (if, for instance, the level of effort necessitates more time for research and development)

Epic	Capabilities	In SmartSheet	Comments	GitHub ID
Landing Page and Authentication	Integration with existing HSES authentication methods, relying on them to handle new user creation and forgot username/password flows.	Yes	The MVP landing page will be kept very simple, just some welcome content and a login button; so we'll handle it in the same epic handling that login button.	25
Authorization/Permissions	User permissions to enable defaulting display of topics based on role and region. A basic admin UI for managing the permissions for exclusive use by Ryan and possibly Krys.	Yes		34
HSES Data Integration	In Activity Reports, display Grantee names and Grant ID numbers based on what's in HSES.	Yes	Implementation notes: We have 3 options for getting the data: direct integration with HSES (could be tricky); pull through the ECKLC API (great if it works); or, worst case scenario, use spreadsheets already set up for SmartSheet and punt direct integration to a future release.	35
Home Page	Searchable and filterable view of activity reports. Use cases: view all topics discussed at activities with one grantee view all grantees at which a particular topic was discussed view all grantees (across regions) at which a particular resource was used for TTA view all activity reports addressing a particular objective (per grantee or across a region or regions). easily find/edit a report to which the current user was added as a collaborator For consideration: ability to launch the Smart Hub from a grantee-specific view in HSES and have the Home page, after login, default to a view of the Activity Reports list that is filtered to that grantee	No	Nice to have (not yet committed for MVP): Default display is pre-filtered by region and user role.	36
Activity Reports	Ability to create, save, and update activity reports Ability to create a report for a non-grantee activity topic standardization (i.e. alignment of topics with ECKLC website) data filtering based on user role and/or region (e.g. topics, grantees/grant IDs) specificity of what's reported (e.g. ability to indicate multiple activities, each with its own specific topic + objective + goal + activity type + etc.) ability to set activity report status (ready for review, needs changes, complete/approved) a view of reports that are ready for managers to review view of activity reports that have received edit requests from managers default display of goals entered in the goal-setting SmartSheet for this associated activity	Yes (though not with all these great capabilities)		8
Import Data from SmartSheet version of Activity Reports	The Activity Report SmartSheet that went live in the first week of September will gather valuable data tied to the latest group of TTA specialists whose contracts commenced on Sept 1, 2020; so we will preserve this data by getting it into our database.	Yes	Implementation notes: work to standardize topics and goals in the MVP will mean the topic and goal data in SmartSheets may not fit with the new terms. We will store this data in a way that makes it recognizable on the backend as legacy data while working to make its difference from newer data invisible to our users in the UI.	37