Impact Sprints: Bonnie and Karen Weekly Meetings

[kcoronel]

Overview

Meeting Agendas for 1-1 meetings between Bonnie and Karen during the Impact Sprints (July 17-October 14)

Action Items

To create a new agenda

• Copy the template below into a new comment
• Edit the text you pasted with new items for your agenda
• Add the link to the new comment with its date under Resources/Instructions

Resources/Instructions

Impact Sprint Project Plan
BallotNav CFA Impact Sprint Folder
FoodOasis example volunteer backend

Template for next meeting agenda

## [Date] Agenda  and notes

### Prework
- [ ] issue for audit [to be added once there is an issue]

### Roll Call

#### Recurring items: 
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each PM
       - [ ] [Bonnie](https://github.com/hackforla/admin/issues/assigned/ExperimentsInHonesty)
       - [ ] [Karen](https://github.com/hackforla/admin/issues/assigned/kcoronel)
 - [ ] continue adding labels to the issue that are still missing them (see audit links above)

#### New Items
- [ ] 
- [ ] Make new agenda for next week
  - [ ] Carry forward the "New Items" that we did not get to look at today

#### FYIs

#### Notes from meeting

#### Items for next week's agenda

[kcoronel]

[Date] Agenda and notes

Prework

• N/A

Roll Call

Bonnie
Karen

Recurring items: Happens on the PM Sunday meeting

• Accountability and Support Check.
  • Review assignments for each PM
    • Bonnie
    • Karen
• continue adding labels to the issue that are still missing them (see audit links above)

New Items

• [ ]
• Make new agenda for next week
  • Carry forward the "New Items" that we did not get to look at today

FYIs

Notes from meeting

Objectives:
Have a successful partnership engagement with Vote.org or other potential partners
Decide on an established volunteer engagement

Where we are:

• BallotNav needs to create updates to backend

  • Create a 2-week sprint that prioritizes some of the functions we saw needed updates

• User flow on Figma

Ideas:

1. [Form] Fill out availability

• Primary match:
• Who’s available to cover
• Best match geographically [use GMT+/- for code]
• Who’s closest GMT wise
• Nice to Have: Ex: have affiliation to certain area but located somewhere else geographically
• Preference ranking: state preferred, other two don’t mind, don’t care checkbox
• Match you with folks with the jurisdictions they can cover
  • Need volunteer jurisdiction
    -Override screen - putting someone specific if a state/jurisdiction fails (number of reasons: how many times tried, why?, person with information unavailable)
  • Everytime tried to call- this is logged - calling and VM, calling and rings, calling and put on hold and then disconnected, calling and hold Action 1 - Action 2 - real-time information about the challenges [real time data on how hard it is it get information for validation]
• Metrics on validators ability to be successful -- machine learning to evaluate whether area is easy, or successful despite others having trouble

Challenge: not every jurisdiction is the same

• Does this county have one-number for all jurisdictions
• Does this jurisdiction have all the information for drop-boxes of jurisdiction
  - If answer yes- 1 validator can do this
  - If answer is no - can be subdivided to multiple validators
  What point of process does it break into multiple assignments - and how does it break- do we know all the numbers?

If we have 0 information for location

• Database for how many people per jurisdiction
• How many dropboxes per county (speculative but would help support how many jurisdictions we assign volunteers)
• Estimate 1-5 per 1,000,000(population) of ballot drop boxes
• Total number of an estimate of 12 ballot boxes

Current states that don’t do ballot drop boxes:
Texas?
Tennessee?
Others?

EXAMPLE OF VOLUNTEER WORKFLOW

• First level - assigned to a jurisdiction
• Call jurisdiction, do you have information for all counties
• Duplicate records
• Add multiple addresses
• Find all contact info
• Notes section that can travel with you during workflow

Items for next week's agenda

• Karen: make comments to project plan as necessary
• Karen: list of 10 partner organizations in addition to Vote.org BallotNav Potential Partners
• Karen: competitive analysis for either making volunteer opportunities open to all or keeping them internal to the CFA family. Idea: Amazon Mechanical Turk
• Karen: create a PM listing for BallotNav
• Bonnie: Get screen shots of Food Oasis volunteer management backend (Bonnie found login via 1password Food Oasis dev-ops vault)