Open tan-zhou opened 3 years ago
@rjdoria - I provided a possible starting checklist above to help you with attacking this process. Feel free to adjust as you see fit.
Reference for Survey Template: https://github.com/hackforla/product-management/issues/23
Text from figma
Communities of Practice started at Hack for LA in 2020, post-Covid. These communities have been a vital connection point in our fully remote organization. They have enabled us to connect people across projects in ways that are both meaningful for the individuals, and have helped the organization build professional infrastructure to support our community, nonprofit and government project partnerships. These communities have also enabled Hack for LA to provide rapid response to the evolving crises of 2020.
If you would like to join one of the Communities of Practice that has a regular meeting time, join their slack channel and look for the meeting details, usually pinned or in the description. Otherwise see the "How to get started" sections below.
@tan-zhou and @rjdoria plan to have a work meeting 2/1 2 PM PST to create the process document
Roster sheet for CoPs
Sample roster for Ops
see #116 for details
Each CoP leads at the beginning of the meeting should ask if people have access to the google drive by sending a message into the chat with a link to the roster that says:
Please try to open this document. If you can't open it, please put your email address here in the chat, and I will add you to the google drive for our community of practice.
Then once they do that, you add them to the google drive and then tell everyone to try to the roster link again. Add themselves.
Once all have been added, slack bonnie or olivia their github handles and the name of the CoP so that they can be added to it.
Make a repo for all the CoPs and add to the readme:
Draft definition of CoPs:
A Community of Practice (CoP) is defined as a group of people who “share a concern or a passion for something they do and learn how to do it better as they interact regularly.” The purpose of establishing these CoP’s is to help volunteers reach their fullest potential by providing resources and training specific to their area of practice. In doing so, the CoP’s help prepare volunteers with the technical skills in their desired area and to work collaboratively in an Agile team environment.
At Hack for LA, this purpose is manifested in two ways. The first way is the collection of templates, guides, and best practices we utilize to develop our pipeline of volunteers for workforce readiness. This also includes the technology solutions that are piloted and scaled to deliver these resources. The second way is the volunteers themselves, along with the expertise they bring to the organization and the relationships they build outside the organization. The matching of people to projects takes into account their desired technical skills and the availability of more experienced volunteers for guidance and mentorship. This transfer of knowledge from experts to the less experienced is critical to the sustainability of each CoP as volunteers enter and exit the organization over time.
@rjdoria - Would you mind checking off the task list above with the items that have been done?
@rjdoria - Here's one of the older Directories for UX/UI Volunteers. It might be a good idea to create tabs for every discipline and have people input their info as they onboard. Eventually we could use these directories/rosters to track trends on how many volunteers come and go, "are active", etc on a monthly basis.
Updated Checklist for establishing a community of practice
Community Establishment
Overview
We will document the process for establishing Communities of Practice at HfLA. This process will result in the creation of a template that can be scaled across the organization for bringing in new volunteers.
Action Items
Resources/Instructions
Civic Opportunity OKRs Civic Opportunity Project One-Sheet Community of Practice figma page Track project Initiatives #63 Survey Template