# Capacity planning and the Spotify model: tribes, squads, and chapters without a second org tool

> How to run a tribes/squads/chapters org with a capacity planning layer: programs, hierarchy, PI lite cycles, and conflicts — without replacing Jira or a full agile org tool.

- HTML: https://www.simpleworkload.com/en/blog/spotify-model-tribe-squad-capacity-planning
- Markdown: https://www.simpleworkload.com/en/blog/spotify-model-tribe-squad-capacity-planning.md

## Can Workload support the Spotify model (tribes, squads, chapters)?

Yes, as an opt-in capacity and portfolio layer: Spotify terminology profile, program = tribe, squad/chapter hierarchy, PI lite cycles, and conflict detection. Workload does not replace Jira (squad backlog) or a full org tool (guilds, coaching matrix). Free tribes/squads Excel pack at /transformation-spotify-it — 14-day Workload trial.

## Can Workload support the Spotify model (tribes, squads, chapters)?

      **Yes, partially.** Workload covers the capacity and portfolio layer: Spotify terminology profile, program = tribe, squad/chapter hierarchy, PI lite cycles, and allocation conflicts. It is not a full agile org tool — guilds, squad backlog, and coaching matrix stay in Jira or your delivery stack.

      Since *Spotify Engineering Culture*, many IT departments adopt **tribes / squads / chapters** to balance squad autonomy and cross-team coordination. The hard part is **real capacity**: who is available, on which projects, with which conflicts at tribe and squad level.

      **Free resource:** still on spreadsheets? Download the [tribes & squads Excel pack](/transformation-spotify-it) (4 sheets, EN/FR) from the dedicated landing page.

## What Workload covers (and what it doesn't)

### Covered

        - **Spotify terminology profile**: tribe, cycle, squad, chapter labels (opt-in)

        - **Program = tribe**: teams, projects, capacity roadmap, dependencies

        - **Squad/chapter hierarchy**: squads under tribe containers, cross-cutting chapters

        - **Cycles (PI lite)**, objectives, predictability, read-only Jira/ADO epic sync

        - **Allocation conflicts** and portfolio at team/project level

        - **Business roles** tribe lead / Product Owner at program level

### Out of scope

        - Guilds, coaching matrix, full agile culture tooling

        - Squad product backlog and story management

        - Multi-team PI Planning board like Jira Align (post-MVP roadmap)

      Product page: [Spotify IT transformation](/transformation-spotify-it). Module: [Scaled Agile IT](/scaled-agile-it).

## Excel, Jira, or capacity tool: where is the gap?

      Most Spotify transformations fail quietly on one point: **no one sees net capacity at tribe level**. Each squad keeps a file, chapter leads get Slack requests, PMO consolidates in slides. Decisions are made on commitments, not available days.

          NeedExcelJira / LinearWorkload (capacity layer)

          Squad backlog & deliveryNoYesNo (stays in Jira)
          Net capacity per squadPartial (manual)Partial (plugins)Yes (native)
          Tribe / program viewPartial (consolidation)Partial (portfolio)Yes (program = tribe)
          Allocation conflictsNoNoYes (detection)
          PI lite cyclesNoPartial (depends)Yes (opt-in)

      Compare: [Workload vs Jira Align](/comparaison-jira-align). Capacity foundations: [IT capacity management](/gestion-capacite-it).

## Mapping tribes, squads, and chapters in Workload

      **Tribe → program.** A program groups squads, linked projects, budget, and capacity roadmap.

      **Squad → team.** Each squad has net capacity; allocations and conflicts are visible per squad.

      **Chapter → cross-cutting team.** Chapters are modeled as CHAPTER teams, parent tribe or transverse.

      **Cycle → PI lite.** Dates, objectives, and capacity review — align commitment with capacity, not a full Align board.

      See also: [IT program management](/gestion-programmes-it).

## Roles: tribe lead, RTE, PMO

        - **Tribe lead**: validates squad capacity before cycles, escalates chapter conflicts.

        - **Program Product Owner**: prioritizes tribe initiatives vs available capacity.

        - **PMO / IT leadership**: multi-tribe portfolio, budget, executive KPIs.

        - **Chapter lead**: negotiates scarce profiles with allocation visibility.

## Common Spotify transformation mistakes

      **Renaming without capacity modeling** — start with tribe → squads → available days, even in Excel.

      **Buying a second org tool before fixing capacity** — capacity layer first, visual portfolio can wait.

      **Ignoring chapters in allocation** — rare profiles get double-booked across squads.

      **Cycles without weekly capacity review** — PI lite becomes decorative without a 30-minute weekly ritual.

## 30-day starter checklist

        - Week 1 — Enable Spotify profile + scaled agile flag on a pilot

        - Week 1 — Map squads/chapters; import net capacity

        - Week 2 — Create programs (tribes), link projects and teams

        - Week 2 — Connect Jira/ADO read-only for epics and dependencies

        - Week 3 — Run first PI lite cycle with weekly capacity review

        - Week 4 — Measure conflicts resolved vs Excel baseline

      Method: [30-day capacity planning checklist](/blog/comment-mettre-en-place-Capacity-Planning). Excel pack: [Spotify transformation landing](/transformation-spotify-it).

## FAQ

### Should we leave Excel?

      The pilot goal is to centralize capacity and conflicts. Export and API v1 still feed BI. The Spotify Excel pack helps phase 0 or holdout squads.

### Does Workload replace Jira?

      No. Squad backlog and delivery stay in Jira. Workload carries capacity, program portfolio, and cycles.

### Is it SAFe-compatible?

      Yes. Opt-in terminology profiles (standard, SAFe, Spotify) on the same capacity + programs layer.

### Does Workload implement Spotify guilds?

      No. Guilds, coaching matrix, and squad product backlog stay in Jira, Linear, or your delivery stack. Workload covers tribes/programs, squads/chapters, capacity, PI lite cycles, and conflicts.

### Can we use Workload without mandating SAFe?

      Yes. Terminology profile is opt-in (standard, SAFe, or Spotify). You can enable programs and capacity only without imposing a framework org-wide.

## Next steps

      [Spotify IT transformation](/transformation-spotify-it) · [Scaled Agile IT](/scaled-agile-it) · [IT program management](/gestion-programmes-it) · [IT capacity management](/gestion-capacite-it) · [Free Workload trial](/register)

## Sitemap

- [Markdown sitemap](https://www.simpleworkload.com/sitemap.md)
- [XML sitemap](https://www.simpleworkload.com/sitemap.xml)
- [llms.txt](https://www.simpleworkload.com/llms.txt)
- [llms-full.txt](https://www.simpleworkload.com/llms-full.txt)