Every team has its own responsibilities, but there are also responsibilities shared between teams. This document outlines the responsibilities that every team should have. If you're looking for the responsibilities of a particular team, please refer to that team's knowledge base.
- Onboarding documentation for new members (knowledgebase and courses)
- Documentation of past/current decisions
- Documentation of direction decisions.
- Choose the team’s direction (e.g. art direction).
- Avoid trying to make major direction changes without proper process (e.g. https://trello.com/c/32PiVWSd)
- Most teams don't need a separate Trello. If your team has a Trello, you should manage it.
- Teams cannot track their tasks outside the Action Trello. Every team uses the one Action Trello to manage task flow.
Not relevant to programming
- As a team you will complete tasks. Everyone needs a way to access the completed work. Don’t use proprietary, insecure systems like Google Docs or Drive. Use systems like Discord where the end results are viewable by all and not deletable by all. Most teams will use the Asset Discord.
- Give Introduction Chats to new people wanting to join
- Review team tasks
- Empower individuals to meet their career and mentorship goals
- Make sure team members show up to team meetings.
Since we are a hobby team, the reality is people get jobs and stuff happens. We need teams to appoint one person per week to recruit new members to bring in new talent.
Guide to recruiting people to your team
- Elect Servant Leaders and Directors
- Replace Servant Leaders or Directors who are inactive/insufficient.
- When your team is stuck due to lacking something they need, it's crucial to unblock the team by sending someone to communicate the issue.
- Make tasks for other teams using the Action Trello requesting assets.
- We all must use the one central Kanban board and keep it clean.