[30k]: Delivery dashboard

[widal001]

Key links

• Deliverable specification
• Simpler Grants.gov full roadmap
• 10k milestones

Description

• What: Release a basic public dashboard that allows internal and external stakeholders to track key sprint and delivery metrics for the project.
• Why: Publishing our metrics publicly encourages us to define and track key measures for each deliverable and builds public trust in the approach we’re taking. Tracking metrics around sprint and delivery, in particular, will help us scope and plan future deliverables more accurately by enabling us to understand team capacity and delivery velocity.
• Who:
  • Project maintainers who want to monitor team capacity and delivery velocity
  • Internal and external stakeholders who want to monitor our progress toward key deliverables

Note

For more information about this deliverable, please refer to the deliverable specification linked above.

[EOKENAVA]

Weekly Update

What has been done?

Met with Billy and team to discuss questions around how to get from 0-1 and what features will bring the most value

Status
Planning

Risk
Curtis still needs to assign a data engineer to this task with the appropriate skillset.

Deliverable Date
TBD

What will be done?

• Curtis to assign a personnel to work on task
• Will investigate the feasibility and timeline for adding the sprint and delivery metrics to the Looker dashboard he shared
• Nava will will propose changes to the delivery dashboard spec based on Aaron's findings
• Billy will work on refining and moving this brain dump about the vision for Simpler.Grants.gov analytics dashboard into GitBook

[coilysiren]

I'm going to try to scope some discovery work where I deploy AWS Redshift and AWS Quicksight

[coilysiren]

#1411
#1410

[EOKENAVA]

Weekly Update

What has been done?

• Completed technical Planning for Delivery Dashboard 30K
• Discussion about goals and scope

Status
On Track

Risk

• Curtis still needs to assign a data engineer to this task with the appropriate skillset.
• Finalizing tasks and scope

Deliverable Date
April 30th

What will be done?

• Curtis to assign a personnel to work on task
• Discovery on BI tools
• Public Dashboard Design Discovery - Create a Figma mockup for a dashboard page on simpler.grants.go

[sarahknoppA6]

@EOKENAVA is there any update about the Nava review of the deliverable spec? Last update & discussion earlier this week indicated feedback from Nava would be coming, but we need to know when.

[acouch]

We have a suggestion to move the work to two 30ks that has a high-level endorsement. The April delivery date is still on track. We need to circle back with @widal001, hopefully next week to hammer out the task details. From there we can update the date if necessary.

[EOKENAVA]

Weekly Update

What has been done?

• Completed technical Planning for Delivery Dashboard 30K
• Discussion about goals and scope

Status
On Track

Risk

• Curtis still needs to assign a data engineer to this task with the appropriate skillset.

Deliverable Date
April 30th

What will be done?

• Curtis to assign a personnel to work on task
• Breakdown tasks under 30k
• Public Dashboard Design Discovery - Create a Figma mockup for a dashboard page on simpler.grants.gov

[sarahknoppA6]

@widal001 see previous comment a couple of comments up- did the team follow up with you on this?

[sarahknoppA6]

@EOKENAVA @margaretspring please phrase the risk as an if/then statement. Also, I believe we'd like to discuss today at ToT if there is anything that can be done/started on the delivery dashboard in the absence of the data engineer. cc @lucasmbrown-usds

[acouch]

We will have a decision for the dashboard and storage by the end of the sprint.

We will still need to go through the process of creating and estimating the 10Ks and getting approval.

[margaretspring]

Weekly Update

What has been done?

• Completed planning for Delivery dashboard - Planning 10K
• Identified 10K for Designing Simpler analytics dashboard, started [Task]: Public Dashboard Design Discovery #1367
• Discussion about goals and scope
• Presented bisected Delivery Dashboard proposal (Simple.grants.gov reporting that's mre end-user oriented & positions us for later iteration. Public GitBook with reporting that might be less approachable for general public, but end-uer iteration will guide transition other reporting venue). Writing up tickets for implementation
• Data scientist onboarding with MH (https://www.linkedin.com/in/ebuwa-evbuoma-fike/)

Status
On Track

Risk

• on-boarding new personnel

Deliverable Date
April 30th

What will be done?

• Curtis to assign a personnel to work on task -
• Breakdown tasks under 30k
• Public Dashboard Design Discovery - Create a Figma mockup for a dashboard page on simpler.grants.gov

[margaretspring]

Weekly Update 4/3

• [10k]: Delivery dashboard - ETL
  • status: still being pointed
  • agreement reached on implementation strategy through meetings
• [10k] Delivery dashboard - Infrastructure
  • status: still being pointed
  • work under way on setting up datastore (postegres) and BI tool (tbd). setup service for ETL
  • completed
    • [Task]: Delivery Dashboard - Fail CI when there are outstanding linter changes #1541
    • [Task]: Delivery Dashboard - Dockerize the analytics application #1540
    • [Task]: Delivery Dashboard - Create analytics postgres database #1535
    • [Task]: Delivery Dashboard - Deploy application to AWS ECR #1546
    • [Task]: Delivery Dashboard - Deploy application to AWS ECS #1547
• [10k]: Delivery dashboard - Planning
  • status this is still being pointed
  • planning tickets are all created
  • completed
    • [ADR]: Business Analytics Data Storage #1506
    • [Task]: Identify LOE for Supporting AWS QuickSight vs Hosted BI Tool #1509

What has been done?

• Deliverable Specification/30K reviewed & commented by implementation team
• Planning mostly completed, estimates not yet made

Status
Planning/implementation

Risk

• If Deliverable Specification/30K uncertainty continues, timeline will be impacted as team juggling known & unknowns to plan 10K & tasks
• April 30 date is close w/ decision delays

Deliverable Date
Currently slated for April 30

What will be done?

• Nava leads to comment on sections of Deliverable Specification/30K needing clarification/unknown until further into work.
• Getting Embuwa engaged with tasks supporting work
• Mapping known 10K/tasks/milestones while working through areas needing clarification
• Close out ADR for business analytics data storage
• Deploy application to AWS ECR
• CI is modified to fail when there are outstanding linter changes
• Identify LOE for Supporting AWS QuickSight vs Hosted BI Tool
• ADR for business intelligence tool for dashboards

[margaretspring]

Weekly Update 4/11

• [10k]: Delivery dashboard - ETL
  • status: still being pointed
  • tickets refined
• [10k] Delivery dashboard - Infrastructure
  • status: still being pointed
  • finished setup not blocked by ADR decision and ETL implementation
  • completed
    • [Task]: Delivery Dashboard - deploy staging and prod analytics applications
      #1625
• [10k]: Delivery dashboard - Planning
  • status this is still being pointed
  • ADR for BI tool underway

What has been done?

• Deliverable Specification/30K reviewed & commented by implementation team
• Planning mostly completed, estimates not yet made

Status
Planning/implementation

Risk

• If Deliverable Specification/30K uncertainty continues, timeline will be impacted as team juggling known & unknowns to plan 10K & tasks
• April 30 date is close w/ decision delays

Deliverable Date
Currently slated for April 30

What will be done?

• Nava leads to comment on sections of Deliverable Specification/30K needing clarification/unknown until further into work.
• Getting Embuwa engaged with tasks supporting work
• Mapping known 10K/tasks/milestones while working through areas needing clarification
• Close out ADR for business analytics data storage
• Deploy application to AWS ECR
• CI is modified to fail when there are outstanding linter changes
• Identify LOE for Supporting AWS QuickSight vs Hosted BI Tool
• ADR for business intelligence tool for dashboards

[widal001]

Updated the ticket format to reduce discrepancies with the deliverable spec.

[margaretspring]

Weekly Update 4/17

Milestones: [10k]: Delivery dashboard - Planning (100% done) | [10k]: Delivery dashboard - ETL (10% done) | [10k] Delivery dashboard - Infrastructure (50% done) | Delivery dashboard - Enhancements and fast follow (0%)

What has been done?

• ADR for BI tool accepted
• Metabase setup started
• Tickets refined

Status
In Progress

Risk
SIA approval for Metabase

Deliverable Date
TBD

What will be done?

• Metabase setup

[margaretspring]

Weekly Update 4/24

What has been done?

• BI tool ADR re-evaluation - Current status is sticking with Metabase
• Conducted Stakeholder User Interviews
• Drafting & reviewing tech spec
• Beginning implementation of the BI Tool set up

Status
In Progress

Risk

• If during implementation, we learn things (such as how the selected tool can or can't meet security requirements) that make us need to switch our planned approach to the BI tool, then it could take longer to complete this than expected.
• Likewise, current re-evaluation has already caused small delays (Currently deployment of docker image to ECS was targeted for Sprint 22 completion & will likely roll into next Sprint bc starting now), if such delays continue the delivery date could need to be revisited.

Deliverable Date
Sprint 25 - Jun 11

What will be done?

• Additional stakeholder User Interviews to be conducted & are in scheduling process
• Complete Tech Spec
• Continue setting up BI tool

[lucasmbrown-usds]

What does "If further BI tool questions come up" mean? Do you just mean questions about whether the tools work for our security requirements etc? Something like, "If during implementation, we learn things (such as how the selected tool can or can't meet security requirements) that make us need to switch our planned approach to the BI tool, then it could take longer to complete this than expected"?

[acouch]

This was referring to the security questions.

[margaretspring]

Weekly Update 5/1

What has been done?

• BI tool chosen
• Metabase setup in lower environment
• Determine escalation path to procure Metabase Pro

Status
In Progress

Risk

• If Metabase Pro isn't procured, BI tool efforts and moving forward will be blocked and delivery date will need reassessment once license procured.

Deliverable Date
Sprint 25 - Jun 11

What will be done?

• Further configuration of Metabase
• Start of ETL work

[acouch]

Weekly Update 5/8

What has been done?

• Dashboard stakeholder interviews
• Metabase chosen (ADR updated)
• Metabase app (not connected) deployed to AWS
• ELT work initiated

Status

• In Progress

Risk

• Blocked on Metabase procurement

Deliverable Date
Sprint 25 - Jun 11

What will be done?

• ETL setup and deployment to tranfer data from github to the analytics database

[widal001]

Replacing our old deliverable tickets with a new ticket format