How agile scales beyond one team (Scrum of Scrums, LeSS, Nexus, SAFe) and how PSM, CSM, PMI-ACP and SAFe certifications compare.
Why it matters
Scrum and Kanban were designed for a single small team. Real products are often built by many teams at once: a bank's mobile app might involve ten teams, a shared platform team and a security team. Scaling frameworks try to keep those teams aligned without losing agility. You will also see agile certifications in almost every IT project manager, scrum master and analyst job advert, and it helps to know what each one actually tests.
Why scaling is hard
When several teams work on one product, new problems appear:
- Dependencies: team A cannot finish until team B changes an API.
- Integration: each team's work must combine into one working product.
- Priorities: whose backlog wins when two teams need the same people?
- Alignment: everyone needs the same picture of the product goal.
The best first step is usually to reduce the need for coordination (organise teams around features or customer journeys so each can deliver end to end) before adding coordination layers.
Common approaches
| Approach | In one line | Typical size |
|---|---|---|
| Scrum of Scrums | A representative from each team meets regularly to sort out cross-team dependencies | 2 to 10 teams |
| Nexus (Scrum.org) | 3 to 9 Scrum teams share one Product Backlog and one Product Owner, with a Nexus Integration Team | 3 to 9 teams |
| LeSS (Large-Scale Scrum) | One Product Owner and one backlog for many teams, keeping Scrum as simple as possible | 2 to 8 teams (LeSS Huge for more) |
| SAFe (Scaled Agile Framework) | A detailed framework with roles, events and artifacts at team, program (Agile Release Train) and portfolio levels | 50 to 125 people per release train; many trains |
| Disciplined Agile (now part of PMI) | A toolkit for choosing your own way of working rather than one framework | Any |
SAFe in a little more detail
SAFe, from Scaled Agile, Inc., is the most widely adopted scaling framework in large enterprises. Its core idea is the Agile Release Train (ART): a long-lived team of agile teams (typically 50 to 125 people) that plans together in a PI Planning event every Planning Interval (PI; called a Program Increment before SAFe 6.0; usually 8 to 12 weeks), then delivers in synchronised iterations. It adds roles such as the Release Train Engineer and Product Management, and uses prioritisation by WSJF (weighted shortest job first).
Supporters value its clarity and its fit with large organisations. Critics say it can add layers of process and that "agile" becomes a label on traditional planning. Both views are worth hearing; the framework works best where leaders genuinely adopt its values. Read the framework itself at scaledagile.com. Checked on 2026-10-23.
The main certifications
Certifications show employers that you know the vocabulary and the framework. They do not replace experience. Requirements, prices and exam formats change, so always check the official page. All links checked on 2026-10-23.
| Certification | Body | What it involves (in general terms) | Good for |
|---|---|---|---|
| PSM I (Professional Scrum Master) | Scrum.org | An online assessment based on the Scrum Guide; a course is optional; the certification does not expire | A rigorous, lower-cost test of Scrum knowledge |
| CSM (Certified ScrumMaster) | Scrum Alliance | A required live course with a Certified Scrum Trainer, then an exam; renewed periodically | Learning in a classroom with practice and networking |
| PMI-ACP (Agile Certified Practitioner) | PMI | Requires agile project experience and agile training, then an exam covering several approaches (Scrum, Kanban, XP, Lean) | People with experience who want a broad, method-neutral credential, often alongside PMP |
| SAFe certifications (for example SAFe Scrum Master, SAFe Agilist) | Scaled Agile, Inc. | A required course, then an exam; annual renewal | Roles in organisations that use SAFe |
Also worth knowing:
- PSPO (Scrum.org) and CSPO (Scrum Alliance) for product owners.
- CAPM and PMP from PMI for project managers; the PMP covers predictive, agile and hybrid approaches.
- For analysts, the IIBA offers the Agile Analysis Certification (AAC) alongside ECBA, CCBA and CBAP. See the IIBA certifications page.
Choosing a certification
Ask yourself:
- What do job adverts in my area ask for? Search 20 adverts for your target role and count.
- What does my employer use? A SAFe organisation values SAFe certificates; a startup may not care.
- Do I need structured teaching? Course-based certificates (CSM, SAFe) include it; assessment-only ones (PSM I) let you self-study from the free Scrum Guide.
- Do I meet the experience requirements? PMI-ACP and PMP require documented experience.
For someone starting out, a common route is to read the Scrum Guide closely, practise on real or volunteer projects, then take one entry-level certificate that local job adverts mention.
Common mistakes
- Scaling before one team works well. Scaling a dysfunctional process multiplies the dysfunction.
- Adopting a framework wholesale without adapting it to the organisation.
- Collecting certificates instead of experience. Interviewers ask for examples, not acronyms.
- Trusting old blog posts for exam details; check the official body.
Quick recap
- Scaling adds coordination across teams; first reduce dependencies by organising around features.
- Scrum of Scrums, Nexus and LeSS keep things light; SAFe is detailed and enterprise-focused.
- PSM I is assessment-based, CSM is course-based, PMI-ACP needs experience, SAFe certificates need a course and renewal.
- Choose by job adverts, employer, learning style and eligibility, and check the official pages.