Team Structure

The goal of the community of practice is to provide the mechanism for members to self organize, build their skills, apply their knowledge, and deliver value for themselves and the community. To that end, the volunteer teams will operate in an organic matter with individual, autonomous teams forming and disbanding based on the interest, need and circumstances at any given point in time. There are a few key concepts we would like to reinforce

Starting a Team

As time goes on, we would like to allow any group of people interested to be able to create their own team. Currently, we are trying to build up a few core teams around basic tactical capabilities the community needs like webinars and editorial content. However, if there is a group of people who wish to start their own initiative, as long as they are willing to abide by the general guidelines outlined below, they are welcome to proceed with the full support of the community

Paired Leadership

Based on our experience with volunteer, distributed teams, we have instituted the practice - adapted from XP - of paired leadership. Specifically, each team will have a pair of people sharing the "project owner role". The point of this arrangement is to provide support and increase availability at meetings. Generally speaking, when starting a new team, we will look to the group to reach consensus about the leader roles. At times, when starting new teams, the board may simply appoint project owners.

Inter-Team Coordination

All volunteer teams must coordinate during our weekly leadership meeting. This meeting is currently scheduled for Fridays at 8:15 AM PDT / 11:15 EDT, but that may change based on people's availability. Each team should ideally have one of their project owners attend, but may opt to appoint a specific liaison. The point will be to report out overall progress for each team, escalate any issues, and organize any activities across teams, such as promoting a webinar event via our social media channels.