Communities of Practice are self-organized, cross-functional groups of Subject Matter Experts (or aspiring to be!) within the CS organization dedicated to a topic within GitLab or the broader DevOps space. The goal is to build assets, best practices, demonstrations, and share experiences we learn from prospects and customers. In turn, CoP will build broader technical depth within our CS organization to better advise our customers and influence our product roadmap.
The content and assets are aggregated into a single group to maximize discoverability. Each Community of Practice has a project which contains a Readme of links and an issue board for discussion.
|Facilitator||Assembles the group, runs the meeting, and maintains the project|
|Member||Any subject matter expert. Participates in meetings, provides input, and contribute to the resources|
|Contributor||Any Team member who engages with the CoP group SME should try to contribute back - such as providing a deck or recording where the information gathered was utilized.|
Anyone can establish or participate in an existing Community of Practice. Below you will find the active ones. If you are interested in starting a new one, please follow the process outlined below.
|Infrastructure As Code||@sri19, @corina_patachia, @kgoossens, @svij, @simon_mansfield, @mkulakowski, @gronk, @pierre_adrien|
|Trusted Advisor Skill Development||Darwin Sanoy (@darwinjs), Chester Nwachukwu (@cnwachukwu)|
There are reoccurring topics from prospects and customers that could be a good fit for a CoP. If you are looking to build a new CoP but unsure what would be most impactful, this is an excellent place to start!
#cp_prefix, so team members know where to go for help.
A Community of Practice does not have a specific timebox; it's an ongoing process that should evolve. Here are some useful methods to follow and review regularly:
It's important to reflect on the group to measure if it's successful and healthy. Here are some suggestions on how to measure:
CoP's are community-driven, and for various reasons, they may decline in participation, so the content becomes stagnant or outdated. If you are a facilitator of the group, check with the team if anyone else wants to take ownership. If not, it's best to archive the group for historical purposes rather than let it linger out-of-date, which could send other team members down the wrong path. In the future, we will add a table on this page for "archived communities."