Squads¶

Characteristics

• Squads are formed by multiple members of diverse guilds with the purpose of achieving a particular clear goal.

• Squads are responsible for the progress of the project.

• Members' seniority or leadership are exclusive to the guild and are not related to the structure of a particular squad, which is only temporary.

• Each Squad has a squad leader, which is the person responsible for getting the thing done.

• Squads are required to have standups at least twice a week while the squad is live.

• Squads and their leaders can be proposed by any member of the organization, but they are approved by the leader of their tribe. If the squad involves a person from another tribe, that tribe leader must also sign off.

• Squads report to their tribe leader or whoever they assign for this task.

• Team members can join live squads, the leader has the authority to approve it, or request it.

• Members can directly contact the entire organization, if it aids in the mission of the squad.

• Each member will state the percentage of their time that will be dedicated to each squad they are a member of, and the sum cannot be higher than 100%.

• When a person joins a new squad, prior to attending any meetings, they should have a one-on-one session with the squad leader where the objectives are clarified and the person agrees to join that squad and structure their time accordingly.

• Consultant role: consultants dedicate very little time and focus to the squad. This person is kept in the loop and belongs to the squad’s Slack/Notion/FigJam pages. They can share opinions, but won't attend weekly follow-up meetings. Joining as a consultant is an official role, and requires approval via the standard process in discussion with the tribe leader. Occasionally someone who is invited to join the squad by the squad leader may end up being approved as a consultant instead. This can be an especially useful role for stakeholders.