Git Product home page Git Product logo

brigade-playbook's Introduction

Brigade Organizer's Playbook Extension Project

Overview

The Brigade Organizer’s Playbook (BOP) Extension Project is an initiative of the Code for America National Advisory Council (NAC).

The BOP Extension Project seeks to build on the existing product and improve its value as a communal, high-value resource for sharing best practices in topic areas such as fundraising, recruiting members, running remote brigades, project management, setting and achieving DEI goals, etc.

🌐 This project is 100% open source, transparent and community led

Project context Each of the 80+ Code for America Brigades generates valuable learnings in topic areas such as fundraising, recruiting members, running remote brigades, project management, setting and achieving DEI goals. What worked and how to replicate some of these are documented in the current Brigade Organizer’s Playbook.

Both the NAC and CfA independently identified the need to have replicable templates of processes and practices as part of their strategic priorities for 2020, to help scale the impact of Brigades' work to transform Civic life through technology.

The initial Scope of Work (SOW) Exploratory interviews with Brigade Organizers - to discover what best practices and processes exist, as well as report on what future needs would improve the ongoing collection and sharing of learnings across the network.

For more information the initial SOW and its milestones, refer to: Brigade Organizer's Playbook One Sheet


How to Contribute

Communication channels

Project Leadership

  • Name: Bonnie Wolfe
    • Role: Agile Mentor & CfA National Advisory Council BOP project Co-Lead
    • email: email
    • Slack: CfA Slack
    • Github: experimentsinhonesty
  • Name: Thad K.
    • Role: CfA National Advisory Council BOP project Co-Lead
    • email: email
    • Slack: CfA Slack
    • Github: thadk
  • Name: Will Pfeffer
    • Role: CfA Brigade Network team representative
    • email: email
    • Slack: CfA Slack
    • Github: willpfeffer
  • Name: Sam H.
    • Role: Product Manager
    • Slack: CfA Slack
    • Github: thesamwong
  • Name: Serena Baleja
    • Role: Product Owner
    • Slack: CfA Slack
    • Github: Baleja
  • Name: Marianne Miranda
    • Role: UX Research Team Lead
    • Slack: CfA Slack
    • Github: MarianneAnthonette
  • Name: Raquel Nishijima
    • Role: Communication Designer & UX Researcher
    • Slack: CfA Slack
    • Github: raquelnish
  • Name: Jon Kropko
    • Role: Data Scientist
  • Name: Jon Kropko
  • Name: Tan Zhou
    • Role: Research Analysis Contributor
    • Slack: CfA Slack
    • Github: tan-zhou
  • Name: Helen Lin
    • Role: Research Analysis Contributor
    • Slack: CfA Slack
    • Github: osnickersnee
  • Name: Myranda Pierce
    • Role: Research Analysis Contributor
    • Slack: CfA Slack
    • Github: myrandi
  • Name: Reem Mehdoui
    • Role: Research Analysis Contributor
    • Slack: CfA Slack
    • Github: reemux
  • Name: Mark Gothard
    • Role: Research Analysis Contributor
    • Slack: CfA Slack
    • Github: mgoth

Past Contributors, with thanks to:

  • Special Projects Coordinator - Naomi Chao CfA Slack

Volunteer management is being provided by the Hack for LA - Civic Tech Structure team.

brigade-playbook's People

Contributors

baleja avatar experimentsinhonesty avatar jkropko avatar marianneanthonette avatar massamh avatar raquelnish avatar thadk avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

brigade-playbook's Issues

Verify need from brigade leads for self-service form for members

Overview

We want to qualify the need as to whether brigade leads want a self-service version of the survey for wider brigade members to understand what they would prioritize and any effective processes and practices they want to share.

Dependencies

  • Conducting enough interviews to determine interest is present

Action Items

  • Add to the google form a question asking whether self-service version of the form is required (UXR to ask the question)
  • Based on confirmation of above, create a self-service version
  • Customize the form for Brigade Members
  • Review the form changes 29th Dec
  • Rename title of form
  • Capture feedback from self-service forms

Resources/Instructions

We have asked your many questions today. Would you be interested in a self-service version of this survey from today for your members. This would show you what they prioritize and any effective processes or practices they want to share. If you answer 'yes', and there is enough interest, you will be invited to a DesignThinking workshop. [If you are asked for further details about the workshop, you can respond with: to find out how we can expand the survey, taking into account how you want to share a larger set of information outside of your brigade].

BOP Brigade Member Interview Form

Build pipeline to get otter.ai transcripts and google form spreadsheet into common spreadsheet

Overview

The google form generates spreadsheet output in which each column matches to a field in the form. We want to also capture the spoken conversation that occurs around each field. The challenge is parsing the otter.ai transcripts and separating the text associated with each field in the Google form, and to do this in a way that can be automatized for all BOP interviews

Dependencies

Otter.ai, google forms, google sheets, Python/pandas

Action Items

  • Pull transcripts from otter.ai into a python env
  • Download the most recent google form spreadsheet
  • Section the transcript by looking for the common language UXRs use to start a question
  • Convert the sectioned transcript to a data frame
  • Merge the data frame with another data frame generated by loading the google form
  • Format the shared data frame and output CSV

Resources/Instructions

Identify Audience for BOP product

Overview

Who will read the reports we will produce and make decisions based of the findings and how will they use it.

Action Items

  • Identify potential audiences for the BOP
  • Identify the decision making process
  • Identifying preference for presentation and consumption

Add related Discourse link to Brigade Assets Column

Overview

BOP Working Group wants to collect all the previously published effective practices in one place, so that we can start to create a data scheme for future effective practices in an accessible way.

Dependency

Wait until all the interviews are done to review assets in the Discourse link and then reach out directly to the brigade leads about those assets if they were not included, to find out why they are not considered valuable at this time.

Action Items

  • Bonnie write to Thad, asking for link that he sent recently.
  • Thad will add link to Discourse.
  • Audit the list and place each link into one of the two categories - based on what is in-development versus in-use

Resources/Instructions

Brigade Asset Column Project Management Board

Discourse Link

Create new issues for all items in WBS

Overview

We need to create issues so that we stay on track throughout the project

Action Items

  • Review the WBS to double check each item to see whether there is an existing issue
  • Create new issue if not
  • Update the WBS & OKRs doc with issue number

Resources/Instructions

BOP Project WBS & OKRs

Review MOCHA & RACI role frameworks to determine applicability

Overview

Volunteers, organizers and org reps need to have a agreed up set of roles, responsibilities and reporting so that all parties will be moving along together towards the finish line!

Action Items

  • Will to send template for MOCHA (please edit this writeup to put the link in the Resources section).
  • Review both frameworks to determine applicability
  • Review project roles against frameworks
  • Annotate the Work Breakdown schedule with chosen framework details

Resources

RACI

  • RACI Links
    Steps to creating a RACI matrix
    RACI blueprint

  • RACI definitions

    • Responsible: People or stakeholders who do the work. They must complete the task or objective or make the decision. Several people can be jointly Responsible.

    • Accountable: Person or stakeholder who is the "owner" of the work. He or she must sign off or approve when the task, objective or decision is complete. This person must make sure that responsibilities are assigned in the matrix for all related activities. Success requires that there is only one person Accountable, which means that "the buck stops there."

    • Consulted: People or stakeholders who need to give input before the work can be done and signed-off on. These people are "in the loop" and active participants.

    • Informed: People or stakeholders who need to be kept "in the picture." They need updates on progress or decisions, but they do not need to be formally consulted, nor do they contribute directly to the task or decision.


MOCA
MOCHA definition via The Management Center

  • Manager: Assigns responsibility and holds owner accountable. Makes suggestions, asks hard questions, reviews progress, serves as a resource, and intervenes if the work is off-track.

  • Owner: Has overall responsibility for the success or failure of the project. Ensures that all the work gets done (directly or with helpers) and that others are involved appropriately. There should only be one owner. There can be multiple owners in some contexts.

  • Consulted: Should be asked for input or needs to be bought in to the project.

  • Helper(s): Assists with or does some of the work.

  • Approver: Signs off on decisions before they’re final. May be the manager, though might also be the executive director, external partner, or board chair.

Respelling for logo

Need to use source image for "Brigade Organizers Playbook Extension project"

image

  • Create a revised graphic with appropriate font and spelling, preferably from original version.
  • Naomi will update Top of form image

Google Drive

Overview

Resolve google drive access to facilitate quick setup and access to templates.

Action Items

  • Check with Tom on access policy and granting rights

Place to store assets we might need for later

Overview

We need a place to store images and other assets for later us in the project so that we don't have to go on hunt for things.

Action Items

  • Add your asset in a comment at the bottom of this issue

Resources/Instructions

codeforamerica.org

Define MVP

Overview

We need an MVP for team and org visibility into process.

Dependencies

  • Persona development 19

Action Items

  • Review personas
  • Gather requirements from manual finding process
  • Gather requirements from onboarding process
  • Gather details around friction during the manual processes (anti-goals)
  • Define ideal feature set
  • Prioritize features by proof of concept, MVP and iterations

Resources/Instructions

Insert link to personas here

Create BOP Readme for Repo

Overview

Communicate the BOP Project goal via a readme file so it is easy for new people joining to understand the project, and get up to speed.

Dependancies

Creation of one sheet #4 - released

Action Items

  • Review with Bonnie the readme file and identify what information is needed and applicable (put notes in comments below)

    • Review the project one sheet and identify which of that information belongs in the readme.
    • Review Civic Opportunity & 100 automations Repository Readme and follow as as a best practice template
    • Review final draft with Bonnie.

Things to include:

Resources/Instructions

Readme template
BOP One Sheet
Civic Opportunity Repository Readme
100 Automations Readme
BOP Extension Project Getting Involved Guide

One-sheet for project

Overview

Write a one-sheet for the BOP project including milestones for the next X months.

Action Items

  • SAM
    • Review VRMS and Civic Opportunity one-sheet
    • Produce First Draft of One-Sheet
  • Sam to convert One Sheet into new BOP brand style
    • Prepare questions for review with Bonnie
  • WILL
    • fill in missing gaps on the history - invite to Tues, Thursday
  • SAM
    • Release dependency #5
    • Populate 'As-is' state, source background information from Will Pfeffer
  • Send One Sheet to Will for approval

Resources/Instructions

All Project One Sheets
VRMS Doc
Civic Opportunity Project One-Sheet

Follow up on P&Ps with brigades using form

Overview

We need to create a version of the survey to send to Brigade Leads to collect P&Ps.

Action Items

  • Make a copy of the form delete all the irrelevant questions
  • Change the instruction text
  • Test internally
  • Make the Bitly link
  • Write the messaging for communicating with the brigades.
    • Provided no links but said they had something to share
    • Link for one process or practice, & said they had more to share
    • Mentioned P&P but said to contact someone else to be able to get the link
  • Pilot by sending link to 2 brigades that have not yet sent us links
  • Post interview email messaging

Resources/Instructions

BOP Process/Practice Collection Form - EDITABLE

Setup Fun Retro

Overview

We need to have fun retro boards setup for feedback on the UX training so that we can reduce the time we spend on Q&A while still getting qualitative information that we can use afterwards.

Action Items

  • Signup for funretro under the [email protected] email
    • Setup two boards for the workshop for questions from the workshop

Resources/Instructions

Fun Retro signup

UX Researcher Recruitment Channel Outreach

Overview

We need to identify and post the recruitment message to all relevant channels to ensure successful recruitment drive of UX team.

Action Items

  • Identify potential channels to post recruitment message
  • Create spreadsheet of channels
  • Draft the message
  • Post recruitment message to pilot number of channels to gauge results
  • Create strategy for how and when to post
  • Execute strategy

Resources/Instructions

Messaging Doc

Determine where we track and report UXR activity

Overview

We need to determine when interviews and assets are completed and have this information readily available.

Action Items

  • Determine where we want to capture and keep track of interview status
  • Determine when assets are uploaded e.g. transcription

Resources/Instructions

Update the readme

Overview

We have added a lot of new resources and work product to the project that we want to be visible and navigable.

Action Items

  • Figure out which items from the project board are not yet on the readme
    • Add items to the readme as appropriate

Resources/Instructions

current readme

Contingency for UXR interview no-shows

Overview

We need to ensure that UXRs join scheduled interviews to ensure expectations met for conducting interviews.

Action Items

  • Send message to UXRs asking to join HfLA Slack and message @ all project team (Marianne, Bonnie, Thad, Sam)10 minutes prior to interview to confirm attendance
    • Add UXR individuals
  • If no-show, then one of Project Team to act as substitute - confirmed via Slack

Resources/Instructions

Mixed methods to qualitative insights from research

Overview

We will enrich and validate research findings with any qualitative research that emerges from quant based answers (1-5 scored questions)

Action Items

  • Otter AI sign up
  • Work flow
    • Otter AI create transcript from voice recordings
    • Create second google form template to capture those additional transcribed findings / import answers into
    • Transcription puts into buckets of what was said where
    • Validate the transcript template after a few interviews
    • Field about who they are - use UXR number + notes field
    • Transcription testing
      • Manual setup of spreadsheet with defined fields per comment
      • Scripted Output from Transcriptions (Python) [details to be found in #49]
      • Testing Procedure UXR [details to be found in #59]
  • Test methodology between Project Team / Jonathan to test [details to be found in #59]
  • Test one UXR manually with pilot [details to be found in #59]
  • Rollout training to wider UXR group [details to be found in #59]

Notes:

  • People who signed up to do UXR research is a role
  • People signing up for transcription is a different role
  • We want to have a validation step, therefore interviewer should not be the transcriber

Resources/Instructions

Transcription Clean Up Template
Transcription Sheet Template
Research Analysis Plan

Design Training and related materials

Overview

We need a plan and materials for running the UXR training.

Action Items

  • make new deck
    • include slides for
    • Agenda (3 min)
    • Overview of CfA and the brigades (2 min)
    • Overview of the project (3 min)
      • History of the BOP
      • Current Mission
    • Instructions (5-10 min)
      • Read
      • [ ]Q & A into fun retro
      • combining and reviewing fun retro questions
    • Pairing off to try delivering the survey to each other, switch off to the e(30 min)
      • ( add notes with q#s to fun retro as you go, use [email protected], select 1 for the first scale question, and 0 for the second, read each one, and choose 1 for all the rest, and only have two processes and practices).
    • Break (7 min)
    • Fun Retro Q & A for questions (15 min)
    • Next Steps
      • Get a UXR number if you feel ready to conduct interview (5 min)
      • Signup for next training if you do not feel ready
    • Add their first two weeks of availability (15 min)
  • email to invite UXRs that have indicated interest via form
  • UXR instructions
  • UXR schedule
  • Fun Retro
  • write follow-up email with links to:
    • UXR instructions
    • BOP UXR schedule spreadsheet in case they need to change their availability

Resources/Instructions

UXR Instructions
BOP UXR schedule
BOP Slide template
BOP Invite for training
UXR Interview training deck
Fun Retros

Place to hold everything that is Out of scope

Overview

Capture potential out of scope activities and related OKRs, to ensure that we are ready to take recommendations into future deliverables as part of a phase 2.

Dependencies

Dependent on decision by CfA and NAC to process to a phase 2

Action Items

  • Capture out of scope activities on an ongoing basis

Create/Refine Personas

Overview

We need to build personas to confirm ongoing path forward.

Dependency

Waiting until we have all or most of the interviews done

Action Items

  • Review Thads sample Personas of FOIA
  • Define the buckets where brigade leaders answers are aligned to identify project personas
  • Document those similarities
  • Choose some representative Brigade Leaders to interview further to fill out the persona

Resources/Instructions

Persona examples from Thad project with City of Boston https://docs.google.com/presentation/d/1Du6_KVTKwBWUB8F71pT6Umj7Xmbcz0TB5uwIfOlbEmk/edit?usp=sharing
feel free to borrow style 🙂

Setup Milestones and Initial Issues

Overview

We need to create milestones and associated issues to manage progress and create visibility against the project deliverables.

Action Items

  • Program manager and Product Manager
    • Review milestones from Civic Opportunities Project and determine those applicable to BOP project.
  • Product Manager
    • Create milestones
    • Review and identify which issues are appropriate
    • Create the issues

Resources/Instructions

BOP Project Initial Issues

Deck for Brigade Congress

Overview

We lighting deck for BC to communicate value of project to potential brigades and uxrs

Action Items

Brigade Congress Presentation

-[ ] links

  • repo
  • one sheet
  • join the team
  • interest form for chat
  • uxr interest form

Resources/Instructions

WBS after the interviews

  • Analyzing & synthesizing data (informed)
    • Trend analysis
      • highest priorities
        • by ALL
        • by Size of Brigade
        • length of leadership
        • by Region
      • Assets
        • by Topic Areas
        • by Readiness
        • by Type
        • by numbers of times mentioned (same asset mentioned by multiple brigades)
      • BOP Awareness & Usage Analysis
        • knowledge of
        • number of people using
        • frequency of use
        • helpfulness
      • Create summary report
      • Affinity Mapping Process to determine themes and insights (refer to the Qualitative Research Practice Guide)
  • Write recommendations (consulted/helper)
  • Presentation of analysis to CfA and NAC
    • Create slide deck to present summary and highlights
      • Now that we have this round of insights, who else do we need to talk to?
      • What areas can we dig into further?
      • What additional questions do we have?
    • Schedule Presentation to CFA and NAC
    • Deliver Presentation
    • Discuss Next Steps & Recommendations (Open call to NAC members to be consulted/helper)

Update Team Roster

Overview

Rolling Roster of team participants.

Action Items

  • Ask Product Lead to add you to the google folder, by slacking them your Gmail address.
    • Add your info to roster. You do not need to fill in columns D and J-N.
    • @ mention Sam when you finish, so he can fill out the unfilled columns.

Resources/Instructions

Team Roster

Notify VRMS of Team Meeting Times

Overview

VRMS (Volunteer Relationship Management System) needs to know details of weekly team meetings

Dependency

  • When project card is on website #9

Action Items

Defined Times:

Weekend - Saturday 8pm (CET) 11am (PDT) 2pm (EDT) 1pm (CDT) 12noon (MT)
Weekday - 6pm (CET) 9am (PDT) 12pm (EDT) 11am (CDT) 10am (MT)

  • Meeting occurrence 1 x weekend (Saturday)
  • Meeting occurrence 2 x weekday (Tuesday, Thursday)
  • Notify VRMS of weekly team meetings once project card issue completed

Resources/Instructions

Set up and transfer data to Airtable

Overview

We need to move data across from Google Docs / Sheets into Airtable platform to help data transferability and extraction.

Action Items

  • Request access from Will for Airtable. Ask the following questions:
    • Can we make some parts private, others 100% public?
    • What are the limitations of usage?
  • Identify fields of data to move across from Brigade Contract Directory to Airtable
  • Second priority to move across Google Expressions of Interest Form to Airtable TBD

Resources/Instructions

Brigade Contact Directory - HfLA Version
UXR Schedule - Brigade Timezone, Regional Reference Page
UXR Schedule

How to handle interview requests for non-Brigade leads

Overview

We need to establish a process to handle interview requests from non-Brigade leads

Action Items

  • Review non-Brigade lead response
  • Determine what message to send
    • New potential Brigade organizer
    • A Brigade member not in leadership
  • Send message

Resources/Instructions

  • New potential Brigade organizer
    Thank your interest in the BOP Project and a Brigade Leader interview. At this time we are only interviewing current Brigade leads. Here's the link to our Project Overview. Can you tell us what your interest is for being interviewed? We would love to help you with any next steps.

  • A Brigade member not in leadership
    Thank your interest in the BOP Project and a Brigade Leader interview. At this time we are only interviewing current Brigade leads and specific Brigade members they identify as having effective processes and practices that we need to document. Here's the link to our Project Overview. If there is popular demand by Brigade leads we will create a self-service version of the interview for Brigades to poll their members.

Validate Information Collection from Interviews

Overview

We need to review the information we intend to/have collected from the interviews with Brigade Leaders, so that we can write a report with the findings.

Action Items

  • Create a schema and a template for data capture and presentation
  • Review the template after the information has come in to identify additional fields
  • Add additional fields
  • Review the template with Network CfA Brigade Network Staff
  • Add any additional fields based on feedback
  • Populate the internal spreadsheet with the assets gathered from the interviews, by looking at the survey data as it comes in.
  • Write a script to automatically post any asset that has a rating of 5 "make resource public" to the public facing spreadsheet. Moved to #120
  • Review the P&P internal spreadsheet next steps per brigade to connect with the brigades that rated their processes as a 4/5 but provided no links or there is other missing information.
  • Follow up with the brigade to be able to add the P&P to the external sheet.

Resources

Google Form Role Expression of Interest

Overview

To determine role interest, general availability, and experience level for UXR Team lead and UXR.

Action Items

  • Set up template to be Hack for LA branded

  • Customise form

    • Description at top that says
      • Hack for LA is recruiting for a variety of UX roles on one-time or ongoing projects
    • Role, interested in, UXR/UXTL
    • Project Interest
    • General availability
    • Experience level
      • 1. No training
      • 2. Have some training
      • 3. Never done it
      • 4. Have done it
      • 5. Expert
    • Tool experience - none required, check all that apply
      • Zoom
      • Recording on phone
      • GoogleSheets
      • GitHub
  • Add link to customizable form in the Getting Involved doc, ReadMe and HfLA Project card

Resources

Getting Involved
Editable version of HfLA Interest Form
Non-editable version of form

Scale recruitment to increase number of Brigade interviews

Overview

We need to scale recruitment via a second communication effort to Brigade Leads.

Action Items

  • Refine communication to send out to Region Slack channels
  • Send communications out
  • Attend Regional calls
  • Western Region Sunday 25th Oct.
  • South Region Brigade Call Sunday 25th (Noon) (Thad joining)
  • Slack outreach 1-1 basis
  • Capture any resistance feedback in Resistance Doc

Resources/Instructions

Monthly Updates to Brigade Network & NAC

Overview

We will provide updates on progress to Brigade network and NAC stakeholders to drive engagement.

Action Items

  • Add location where each item in the update can be found (link to spreadsheet and column, etc.)
  • Update slide deck with this months update.
    • % of the way through the interviews update.
    • Give update on P&Ps being added to the external spreadsheet on a rolling basis & any challenges associated.
    • coming soon phases
    • report on progress against OKRs and milestones
  • Paste update into NAC monthly presentation deck.
  • Update in the issue comment below the next delivery date.

Resources/Instructions

BOP Project Status Sheet
Slide Deck

Finalize and setup Google Form for Survey

Overview

Finalize interview questioning path and form mechanism via Google Forms, so that interviewers have a consistent approach to conducting interviews and data collection.

Dependencies

  • Set up dedicated project style guide - survey and form to replicate. #8

Action Items

  • Copy questions from proposal into new document and update with actual questions from form
  • Add the numbering for the questions
  • Adopt and apply style guide to Google Form
  • Finalize questions and formatting
  • Identify and test with 3 Brigades

Resources/Instructions

Procedure for handling new Calendly reservations

Overview

When a new Calendly reservation comes in from another brigade leader:

  • we should edit the UXR spreadsheet with it
  • ask the two UXRs to sort out who is the primary and secondary according to if a transcriber is needed.
  • add the primary UXR (or both) to the calendly invitation on the [email protected] calendar.

Dependencies

  • Mari's draft to the interviewers will be like: "When to expect it, what to do in the mean time. We will be reaching out to you when your interview is scheduled." She would like to explain the interview time period in that email.

Action Items

  • Check with Bonnie
  • Clarify the interview timeline with Bonnie.

CfA Issue Tracker

Overview

Drive engagement from CfA by providing a matrix of responsibilities aligned to milestones and related issues for CfA input.

Action Items

  • Create matrix identifying milestones, issues, and assigning CfA responsibilities (based on MOCHA template)
  • Team to review matrix
  • Send matrix to Will for review

Resources/Instructions

MOCHA Definition

Create communication guide

Overview

Increase engagement with BOP Playbook by developing a style guide for the overall navigation and visual appearance.

Action Items

  • Define a color guide - using the cfa website style guide for colors
  • Define a typography system - using the cfa website style guide for colors
  • Create key components
  • Send templates to Will for review (informed)

Resources/Instructions

BOP Communications Guide
codeforamerica style guide

Role Identification

Overview

Identify and recruit staff for the BOP project team to deliver the project goal.

Action Items

  • Review the general roles document with Bonnie to determine roles required
  • Identify initial list of required roles with Bonnie
  • Add requirements to current needs doc

Resources/Instructions

General Role Definitions
Project Recruiting Needs

Role Recruitment

Overview

We need to recruit contributors for the BOP project at the outset/or ongoing basis.

Action Items

  • Keep team Recruiting needs up to date throughout life of project.

Resources/Instructions

Project Recruiting Needs

Setup Slack Channel

Overview

We need to have a dedicated Slack channel for the BOP project that encourages outside participation and transparency.

Action Items

  • Discuss options internally with CfA network team
  • Set-up channel name / or authorize use of existing channel for this purpose
  • Add everyone from existing Slack channel to the new/repurposed public channel

Resources/Instructions

Current Slack Channel

Public Slack channel

Audit Issues against Milestones

Overview

We need to review the existing Issues in relation to Milestones to ensure they are phased correctly.

Action Items

  • Review all issues that do not have milestones and label them with the correct milestone

Create OKRs

Overview

Establish a consensus on Project OKRs, propose a framework for meeting these objectives, and how we will measure and report.

Action Items

  • Research OKRs for Civic Opportunity Project, and discuss options with Bonnie, Naomi, and Thad
  • Establish Project Objectives
  • Establish Key Results deliverables for each Objective
  • Review proposal with team
  • Send OKRs to Will for approval
  • Create new issues against each of the WBS items #37
  • Make changes/revisions to OKRs
  • Finalize OKRs

Resources/Instructions

What are OKRs?
Civic Opportunity Project OKRs
BOP Project WBS & OKRs New
OKRs BOP Working document Old

Create interviewee interest form for BC

Overview

We need a form to capture the email addresses of anyone who comes to brigade congress session and indicates interest so that we don't miss people who are not on our original target list

Action Items

  • create new form called BOP interview - Brigade Leader Interest
  • use header from folder
  • wording for top
    • link to one sheet
    • call to action - let us know you are interested in being interviewed
  • add fields
    • email
    • name
    • Brigade name
    • Role

Resources/Instructions

Image assets folder for header

Register of interest form Congress

Create HfLA project card for project

Overview

Provide collateral for the Hack for LA website.

Action Items

  • Gather Items
    • 600 x 400 image
      • Alt image text
    • Name of project
    • Blurb about project
    • Links (github, slack channel url, Testing Site, Live Site, etc.)
    • Any resources for a Getting Started link (a link to a wiki, readme(s) or both)
    • What you are looking for skills wise
    • Status: Active
  • Add project card

Resources/Instructions

See project cards on the hackforla.org website.

Create and Maintain UXR instructions

Overview

We need UXR instructions for the people doing the interviews so that the experience is consistent across all the interviews

Dependencies

Questionnaire form #11

Action Items

  • UXR designer
    • Create a document
    • Add the training questions to it
  • UXR role tester
    • Send feedback on UXR instructions and any changes to be added to final instructions
    • Thad to update google form to pre-populate email address of interviewee
  • UXR designer
    • Update the training questions
  • UXR role tester
    • Send feedback on UXR instructions and any changes to be added to final instructions
  • UXR designer
    • Add Q&As as they come in

Resources/Instructions

UXR Instructions doc
Editable Interview form

Instructions
Name
Know how to pronounce the name of the person you are interviewing before you start the interview if possible.
Use their name, instead of pronouns whenever possible.
If they mention someone else, please refrain from assuming the gender of the person they mentioned, and use they, them if you are unable to use their name.

Geographic info
Know their time zone

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.