Advanced SAFe® Practice Consultant.

ASPC unlocks the advanced SAFe courses you can teach — including RTE, LPM, APM, ARCH, ASE, plus all the role courses you could already teach as SPC. The exact list differs for SPC, ASPC, and SPCT and is maintained by Scaled Agile — see which courses am I allowed to teach?

SPCT (SAFe Practice Consultant Trainer) is the master trainer credential — the highest SAFe certification. ASPC is the prerequisite step before SPCT and authorises you to teach the advanced SAFe courses. SPCT additionally requires Scaled Agile application, mentoring, and an assessment by an existing SPCT.

Scaled Agile recommends at least 6–12 months of active SPC practice — leading transformations, coaching ARTs, or teaching SAFe — before ASPC. There is no formal time minimum, but the case studies and class exercises assume you’ve already taught and led, not just read.

Both. Public cohorts run live-virtual by default; private cohorts (5+ SPCs) are available in-person or remote. Every ASPC cohort is instructor-led by an authorised SAFe Practice Consultant Trainer (SPCT).

SPCT (SAFe Practice Consultant Trainer) — the master trainer credential. SPCT requires application to Scaled Agile, additional preparation, mentoring by an existing SPCT, and a formal assessment. ASPC is the only path to SPCT.

Yes — ASPC has a hard prerequisite. You must hold a current, active SAFe Practice Consultant (SPC) certification before you enrol in ASPC. There is no waiver, regardless of other experience. Scaled Agile verifies SPC status during enrolment.

60 multiple-choice, 90 minutes, passing score 80%. Your first attempt is included. Taken online with a 60-day access window. Retakes are about $250 each at this advanced tier.

ASPC is for people already doing the work who now want to lead it: Principal or Lead Agile Consultant, Transformation Director, and portfolio-level advisory work. Where SPC establishes that you can run an adoption, ASPC is aimed at what comes after — multiple trains, competing portfolios, and executives who have already sat through one failed change programme.

If your engagements are getting larger or more political, yes — that is the gap it addresses. If you are still delivering your first few trains, the honest answer is to spend another cycle doing that first. ASPC assumes real transformation experience to argue with, and the cohort discussion is most of its value.

Inside organisations already invested in SAFe, yes — it reads as “has done this at scale, more than once”. Outside that world it needs the same explanation any framework credential needs, so treat it as evidence supporting your track record rather than a substitute for one. It carries most weight in consultancy selection and in internal promotion to lead-coach positions.

Advising at portfolio and executive level: designing an operating model rather than installing a framework, coaching leaders through the decisions that stall adoptions, and diagnosing why a transformation that looks correct on paper is producing nothing. You also take away the facilitation material for the workshops that get those conversations to a decision.

The questions arriving from executives have shifted. Where the brief used to be “help us scale delivery”, it is increasingly “we have AI pilots everywhere and nothing in production — what is wrong with how we work?” That is an operating-model question, and answering it is the part of the consultant’s job that has changed most.

Start by naming what is actually blocking them, because it is rarely the model. It is usually that nobody owns the decision the pilot was meant to support, the data crosses three teams with different priorities, or the path to production was never designed. We work this as a diagnosis, not a tooling exercise — it is the single most common brief arriving at senior consultants right now.

Its own programme buys focus and almost always builds a second organisation that the first one later rejects. Inside the operating model is slower to start and is the only version that survives. The course covers how to make that argument to a sponsor who has already been sold the standalone version, which is the harder half.

By deciding in advance which classes of decision need a human and which do not, rather than reviewing everything and calling it control. Governance that inspects every output becomes the bottleneck it was meant to prevent — and teams route around it. We work through where the line sits and how to move it as confidence grows.