Agile Squads: Structure, Roles and When to Bring In an Agile Development Team

Updated October 21, 2026 · GIGA IT Editorial Team

Short answer: an agile squad is a small, cross-functional, long-lived team with a clear mission (a product area, a customer journey or a platform) and the autonomy to decide how to deliver it. A typical squad has a product owner, a handful of engineers, QA and, when needed, design or data skills. Squads work when they own a measurable outcome, keep their size small and can release without waiting on other teams.

Related: dedicated development teams · nearshore software development.

If you need a squad but cannot staff it in-house, you can bring in a complete agile development team from a provider. Our guide on how to hire a dedicated development team covers how to choose one, and our dedicated software development team service shows how GIGA IT sets up squads for U.S. companies.

What is an agile squad?

The term became popular with the 2012 paper Scaling Agile @ Spotify by Henrik Kniberg and Anders Ivarsson, which described the squad as “the basic unit of development”: a team similar to a Scrum team, designed to feel like a mini-startup, with a long-term mission. In that model a squad has no formally appointed leader, but it does have a product owner who prioritizes the work. The Scrum Guide gives a useful size reference for any such team: “typically 10 or fewer people”.

The paper described how one company worked at one moment in time; it is not a framework to copy. What travels well are the principles: small teams, long-term ownership, autonomy with alignment and direct contact with stakeholders.

Agile squad vs traditional team structure

Aspect	Agile squad	Traditional (functional) team
Organized around	A mission or product area	A function: backend, QA, design
Skills inside the team	Everything needed to ship: product, engineering, QA	One discipline; hand-offs to other teams
Lifespan	Long-lived; the team keeps its mission	People move from project to project
Who decides how	The squad, within agreed guardrails	Managers and project plans
How success is measured	Outcomes for users and the business	Tasks completed on schedule

Agile squad structure and roles

• Product owner: owns the backlog and the “why”; connects the squad with stakeholders.
• Tech lead or senior engineer: owns technical decisions, code quality and mentoring. Many companies add this role even where the original model did not.
• Engineers: usually full-stack or a backend/frontend mix, depending on the mission.
• QA engineer: builds test automation into the pipeline instead of testing at the end.
• Design, data or DevOps skills: inside the squad when the mission needs them daily; shared across squads when it does not.

As the number of squads grows, companies add structures to keep alignment: groups of squads with related missions (tribes) and communities of practice for each discipline (chapters and guilds, in the Spotify vocabulary).

What makes a squad perform

1. A mission with a measurable outcome. “Reduce checkout abandonment” gives direction; “build features” does not.
2. Autonomy with alignment. The squad decides how; leadership is explicit about what and why.
3. Few dependencies. A squad that needs three other teams to release anything is a squad in name only.
4. Psychological safety. Google’s research on team effectiveness found it was the most important factor among the dynamics it studied: people need to feel safe to raise problems and take risks.
5. A steady rhythm. Short sprints, demos of working software and retrospectives that change something.

How to measure an agile development team

Velocity is useful for a squad to plan its own sprints, but it is a poor way to compare teams. For delivery performance, the DORA research program tracks a small set of metrics: change lead time, deployment frequency, change fail rate, failed deployment recovery time and deployment rework rate. Pair them with one or two product outcomes that match the squad’s mission.

Building a squad: in-house or with a provider

If you have the people, build the squad in-house around a clear mission. If your engineers are already committed to the core product, many companies bring in a complete squad from a provider that offers squad-based development. In that case, check four things: that you meet the actual engineers and tech lead, that the squad works in your repositories and your sprints, that the provider has a written policy for AI tools on client code, and that the contract gives you the code and a clean exit. The full checklist is in our dedicated development team guide, and if you only need one or two specialists, compare it with staff augmentation vs outsourcing.

How GIGA IT works with squads

GIGA IT sets up agile squads of senior engineers based in Latin America who work in U.S. business hours, with AI built into the way they work and a tech lead accountable for delivery. You contract with GIGA IT LLC, a U.S. company incorporated in Texas with its legal address in Houston. Since 2008 we have worked with more than 50 clients in 15 countries. See how we work with client teams, or tell us about the squad you need.

Frequently asked questions

Sources

• Henrik Kniberg and Anders Ivarsson, Scaling Agile @ Spotify (2012).
• Ken Schwaber and Jeff Sutherland, The Scrum Guide (2020).
• DORA, DORA’s software delivery performance metrics.
• Google re:Work, Understand team effectiveness.