Explaining The A To Z Of
Tribe & Squad Structure
Inspired by the Spotify model, Tavisca follows the Tribe & Squad team structure.
On In-House Tribes
A Tribe is a long-running group aligned to a Product Line and is composed of people with cross-functional skills. Every Tribe comprises a Product Manager and a Delivery Manager who work with their tribe members to shape products in a direction that maximizes business impact in a sustainable, agile, innovative & high-quality manner. A Tribe is comprised of typically three or more squads (mission teams).
Within A Tribe
Squads are typically between 8-14 people in size. Every Squad has an Iteration Manager (IM) and a Product Analyst (PA), who help in detailing, scoping, prioritizing, and planning features to be slotted across each iteration. The IM and PA work with the team in ensuring that a culture of agility and impact are fostered within the Squads.
Here’s How They
Work In Tandem
The Delivery Manager helps ensure roadmap delivery success, by helping identify and mitigate Strategic Risks, inter-tribe Dependencies, Capability & Staffing issues and fostering a culture of psychological safety that encourages people to fail-fast, experiment, innovate and thrive.
Collaboration, Mastery, Planned Project Steps
The Advantages We Attain
Tribe members, over time, develop mastery in their domain and a deeper understanding of the codebase, trade-offs, systems, etc. This allows for better Time-to-Market and propensity to create anti-fragile systems.
As each tribe is aligned to a complex domain, they get exposure to a wide variety of challenges over time – technical and business, which gives everyone a chance to work on impactful and hard problems.
Teams are able to balance short term vs. long term decisions since they are responsible for the development, rollout, and health of their own systems, end-to-end.
The coupling across tribes is reduced because of fewer inter-domain dependencies – allowing more autonomous decision making. Of course, there are still some initiatives that can touch multiple tribes and need to be closely managed.
There is a stronger bonding among teams that work together for longer periods, and a sense of ownership & pride towards their product(s).
It allows for each tribe (and product team) to identify and track long-term product-success metrics that help generate feedback on released features – to ensure expected impact.