Organizational Structure: Pods & Tribes

The Badger core team organized itself in Pods and Tribes.

Each project or product becomes a “Pod”.

A Pod has a lead or Pod representative who can represent the Pod in the weekly team meeting and potentially in community calls. The Pod lead is responsible to manage the Pod’s development or work activities and keep the Pod synchronized. Each Pod has an own roadmap. All Pods/projects combined form a general roadmap for Badger DAO.

As soon as a product or project is delivered, a Pod can be closed/archived. There can be Pods for continuous activities, too.

A product Pod can have several team members, eg for tasks and activities as follows:

Pod-wide Communication: A Pod has an own Discord channel for Pod internal communication and to report on the latest updates on product development. There can be various sub-channels in case different Pod members want to discuss a specific topic or work piece. A Pod has an own project/task management board on our task management tool ClickUp.

Let's imagine the Pods to be on a horizontal axis. Since we have different Pods, members can be part of multiple Pods at the same time but don’t necessarily need to be. All Pod members that are responsible for Frontend in their Pod form a Tribe.

The Tribe has its own Discord channel to communicate on Tribe related matters so that knowledge and information can be shared and the Pods don’t become silos.

Communication

In general, we communicate via the Badger Builders Discord channel. Please ask for an invite as soon as you are joining a Pod to work on one of our products.

The Badger team aligns on a weekly basis on the Badger team sync. The badger team sync follows the following setup:

Project/Pod Management