![practicalities-scaling-agile-scrum-or-kanban-neednt-be-choice-rectangle-tcm9-240899.jpg](https://web-assets.bcg.com/dims4/default/73a3154/2147483647/strip/true/crop/950x950+372+0/resize/146x146!/format/webp/quality/90/?url=http%3A%2F%2Fboston-consulting-group-brightspot.s3.amazonaws.com%2Ffa%2Fe7%2F9b5304a7a214dfac5b9d13978cb1%2Fpracticalities-scaling-agile-scrum-or-kanban-neednt-be-choice-rectangle-tcm9-240899.jpg)
Practicalities of Scaling Agile: Scrum or Kanban Needn’t Be a Choice; Think of It as a Continuum
When scaling agile across a company, you want to maintain consistency across the operating model, which includes which process and methods teams use. But be wary of falling into a one-size-fits-all trap. Designing hundreds of portfolios and tribes (groups of squads aligned to a common goal) means not all outcomes will look the same, and the performance of teams will evolve over time. At a high level, a portfolio and squad will probably operate broadly under a Scrum construct, but at a squad level, context differs depending on the squad mission, scope and outcomes being pursued.