civictechindex / BOP

A repo for tracking work regarding the Brigade Organizer's Playbook
10 stars 6 forks source link

Wiki Pages for Editing #182

Open Baleja opened 3 years ago

Baleja commented 3 years ago

Overview

This is to plan the wiki procedure for the next product manager.

Action Items

Resources/Instructions

Procedure

Baleja commented 3 years ago

Welcome to the BOP Wiki!

What is the BOP?

The BOP is short for Brigade Organizers Playbook. It is a collection of resources, examples and processes for running a successful brigade.

Project Overview


play our lightning talk from Brigade Congress 2020
(first 10 min); or review the slide deck (script is in the speakers notes).

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.

Each of the 80+ Code for America Brigades generates valuable learnings and new effective processes and practices currently without a defined pipeline for comprehensive ongoing collection and dissemination.

The initial Scope of Work (SOW) will be discovery, canvassing the BOP end-user (the Brigade Organizers) to understand their pains, wants, and needs, and identifying effective processes and practices (including the state of shareability they are in), through exploratory, structured interviews.

Why do it?

Every brigade has its challenges and successes, This project seeks to collect effective processes and practices from around the brigade network and to identify what resources are most needed so that these resources can be shared and so that as we continue to grow as a network we focus on building what is most needed.

Hasn't it been done already?

CFA brigades have been creating guides as they go, and sometimes these are shared, but not yet in a systematic way.

So how is this different?

As the network has grown, it has become harder to identify priorities and share resources effectively. This project aims to create a framework to comprehensively survey the network and learn from the qualitative and quantitative data, while maintaining transparency.

You can access our project one sheet here.

Baleja commented 3 years ago

Introduction

Welcome to the BOP team! This guide will help get you up to speed on what you need to know to get started as a project team member.


Let's go!

If you have not read the Guide for New Volunteers, please do so.

  1. Read Introduction to the Project if you haven't already read it.
  2. Join our slack communities Code for America & Hack for LA
  3. Join us on the team's slack channel #organizers-playbook and introduce yourself.
  4. Join GitHub or if you already have an account, Slack us with your GitHub handle.
  5. Slack our PM Sam or Serena with your Gmail address and GitHub handle.
  6. If you are working as a UXR, Slack our PM requesting your UXR number.
  7. Accept your Google Drive invite to access the shared folder.
  8. Add yourself to the Team Roster and inform PM after you have done so.
  9. Review the Glossary.
  10. Attend our weekly meetings on Tuesdays, Thursdays and Saturdays for the core team, Wednesdays at 11 for the research team. You can find the links on our project board in the first column on a card called Team Meetings

Who are you?

Click the link that applies to you to find a sequence of immediate action steps:

Roles we are currently recruiting for:

Roles we will be recruiting for soon (express your interest now!):

we will be in contact when we start recruiting for these roles.

If you are looking to join another project immediately, you can check out other projects staffed by Hack for LA, please see Hack for LA's Getting Started guide.


Accessibility standards

Title III of the Americans with Disabilities Act (ADA) requires that all websites be accessible to people with disabilities. The World Wide Web (W3C) Consortium's Web Content Accessibility Guidelines (WCAG) 2.0 Level AA function as the current legal standard for website accessibility.

Get acquainted with accessibility: https://www.ada.gov/pcatoolkit/chap5toolkit.htm

Baleja commented 3 years ago

Name: Bonnie Wolfe

Name: Thad K.

Name: Will Pfeffer

Name: Sam H.

Name: Serena Baleja

Name: Marianne Miranda

Name: Raquel Nishijima

Name: Jon Kropko

Name: Tan Zhou

Name: Helen Lin

Name: Myranda Pierce

Name: Reem Mehdoui

Baleja commented 3 years ago

Process Overview

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

This is our agile process for analysing the needs of Brigade leaders through Interviews, we hope to increase Brigade empathy with this process.

Volunteer User Experience Researchers

All interviews conducted are done by volunteers learning about UXR.

Schedule an Interview with a Brigade Leader

How to conduct a structured interview with Brigade leaders spread across 5 time zones serving over 50 MSA's

UXR Preparation

How to set up and use documents needed to complete the UXR process.

Data Management and Analysis Prep

Handling interview data ready for Analysis.

Interview Analysis

Our methods for analysing qualitative and quantitive data.

Project Tracking

Our work in progress can be seen on our main Github Project Board

Additionally we have some other interrelated tracking tools.


For our brigade wide deliverables please see our Output Page

Baleja commented 3 years ago

Every month we provide a status report to the NAC, you can see the most recent update here. Previous NAC presentations

During the interviews we have gathered many brigade responses with effective processes and practices. Some of these processes and practices are not ready to share (lack of documentation,clarity on how to use, or links to be forthcoming). As the interviews progress we are continuing to update our list of every shovel ready processes & practice for any brigade to use: Effective Brigade Processes and Practices

Our UXR Training Program for Research Interviews

Baleja commented 3 years ago

UXR Program

Becoming a Fast track UX Researcher

In order to be able to operate interviews with 80+ brigades, we needed to prepare a significant amount of User Experience Researchers. After we have scheduled, recorded and stored our interviews in our main tracking sheet, we are ready to verify the data collected.

By completing this training you will fully understand how to:

Understanding Transcription Verification

In this introductory deck, you will discover more about CfA Brigades and the importance of Transcription Verification.

Training Deck

Transcription Verification is ensuring that that verbal answers are reflected correctly in our processes so there is no misinformation. To begin you will need to become familiar with the Transcription Sheet Format

Using these instructions, you will be able to work through a practice sheet of an interview.

When you have completed your practice interview, you will be assigned a real interview to start on.

Understanding Data Organization

Organizing the data of multiple interviews requires scripts that communicate between multiple sheets, dis-organization of data can break the working scripts.

Going through the data organization instructions you will be able to pull all the data that you verified to a centralised master sheet which has all the responses.

Understanding Tagging

Our tagging stage helps us to organize open ended questions which in this case means additional topics, tagging is the first stage of UX where you interpret direct quotes into a single topic or label.
Tagging Instructions

Resources during interview training

Use this quiz as a self assessment in what you learned for UXR Fun Retro Q&A Instructions Review | Interview Practice

Baleja commented 3 years ago

Pre-Scheduling

What to be aware of before reaching out, all interviews must comply with our code of conduct. CfA Code of Conduct

Scheduling Communications

What to message Brigade Leaders to arrange an interview

During the Interview

Scheduling an interview

After the Interview

You will need to ensure that the recording is uploaded to our transcription service Otter.Ai, here are the instructions for setting up the Otter.ai

Baleja commented 3 years ago

Interview Management and Analysis Prep

WIP

Step1. Interview Scheduling: Ensures that interviews are tracked, that each incoming interview is assigned to an interviewer, and that each interviewee receives a copy of their interview responses. (Mari)

Step2. OtterAI Set-up: Ensures that the interview recordings and auto-transcriptions are organized and accessible. (Thad)

Step3. Create and Update 1: Transcription Sheet: Create the transcription sheet and update our internal Tracking sheet. (Raquel)

Step4. Pre-fill Transcription Sheets: Ensures that transcription sheets contain all the interview data and are ready for transcription verification and research analysis. (Thad)

Step5. Create and Update 2: GitHub Issue and P&P: Create the GitHub issue for the UXR Management Project Board with a link to the Transcription Verification and add the Processes & Practices to a specific spreadsheet. (Raquel)

Baleja commented 3 years ago

Step 1. Recruiting User Experience Researchers ### Project Tracking

Step 2. Invite Brigade Leads to signup for Interviews

Step 3. Training for Interviews Additionally we have some other interrelated tracking tools.

Step 4. Interview Management and Analysis Prep - OKRs BOP Working document - New/Work In Progress

Step 5. Interview Analysis

Our work in progress can be seen on our main Github Project Board

ExperimentsInHonesty commented 6 months ago

Review this issue to make sure all this content got added to the wiki