- Identity and Format at a Glance
- How You Qualify and Sit the Assessment
- Fees, Validity, and Renewal: What Is Settled and What Is Not
- Domain 1: The Scrum@Scale Framework
- Domain 2: Patterns of High Performing Teams
- Domain 3: Scaling the Teams
- Domain 4: Scrum Master Cycle
- Domain 5: Product Owner Cycle
- Domain 6: Connecting the Cycles
- Domain 7: The Credential Itself
- Sequencing the Domains Across Four Weeks
- Where the Credential Shows Up at Work
- Frequently Asked Questions
- The issuer's published policy specifies 30 multiple-choice questions, a 75% passing criterion, and up to 2 attempts.
- Eligibility requires at least 14 hours of live instruction with a Registered Scrum@Scale Trainer.
- Complete the assessment within 30 days after your course ends; sessions are untimed and progress is saved.
- The seven domains are unweighted preparation headings, not an official exam blueprint.
Identity and Format at a Glance
This cheat sheet covers the Registered Scrum@Scale Practitioner credential, issued through Agile Education by Scrum Inc. It is not a SAFe credential, not a Scrum.org or Nexus examination, and not the Registered Scrum Master or the Registered Scrum@Scale Facilitator credential. If your study notes mix in vocabulary from those programs, trim them now. Scrum@Scale has its own cycles, its own role names, and its own logic for coordinating many teams.
| Item | What the issuer policy says |
|---|---|
| Issuer | Agile Education by Scrum Inc. |
| Question count | 30 multiple-choice questions |
| Passing criterion | 75% |
| Attempts | Up to 2 |
| Completion window | Within 30 days after the course ends |
| Timing | Untimed sessions, progress saved |
| Delivery platform | Online assessment administered through ScrumLab |
| Prerequisite | At least 14 hours of live instruction with a Registered Scrum@Scale Trainer |
Seventy-five percent of 30 questions means you can afford only a handful of misses, so precision on the framework's specific vocabulary matters more than broad familiarity. For a deeper look at the scoring rule, see our page on the RS@SP passing score.
How You Qualify and Sit the Assessment
There is no standalone "walk in and book a seat" route. Eligibility runs through a course: you need at least 14 hours of live instruction covering the learning objectives, delivered by a Registered Scrum@Scale Trainer. The issuer's course page is the place to confirm what a qualifying class looks like. Recorded-only study does not substitute for the live-instruction requirement.
After the class, the clock matters. The published policy gives you 30 days after the course ends to complete the assessment. Because sessions are untimed and progress is saved, the pressure is not a ticking countdown during the test but a calendar deadline around it. Do not confuse the 14 live-course hours with an exam timer; they are two unrelated numbers.
For the full eligibility picture, read RS@SP requirements and prerequisites, and for scheduling logistics see RS@SP exam dates and deadlines.
Fees, Validity, and Renewal: What Is Settled and What Is Not
What is fixed in the issuer policy
Course tuition is set by the individual trainer, so it varies. The issuer's own credentialing charge is $50 USD per student for legal residents of the top 100 GDP-per-capita countries and $25 elsewhere. That charge is billed to trainers, so it is not a universal standalone candidate exam price. When you see a course price, assume the trainer has decided how to fold the credentialing charge into it.
What is contested
The same issuer policy specifies one-year validity, an annual renewal charge at the same $50/$25 residence tiers, and a brief renewal re-examination that requires 75% with up to 2 attempts. However, provider statements disagree: one training provider's FAQ describes annual renewal, while another provider's page describes lifetime validity. Neither claim overrides the retrieved issuer policy.
Domain 1: The Scrum@Scale Framework
The Scrum@Scale Framework
This is your foundation. The official framework reference is the Scrum@Scale Guide, version 2.1 (February 2022). It is a framework reference, not a weighted examination outline, so use it to understand concepts rather than to guess question counts.
- Scrum@Scale is a modular, scalable way to extend Scrum beyond a single team.
- It is organized around two cycles: the Scrum Master Cycle and the Product Owner Cycle.
- The goal is to reduce complexity by scaling the same roles, events, and artifacts rather than layering on new management structures.
- Know the vocabulary the guide uses for each component, since multiple-choice distractors often swap near-synonyms.
A common trap is importing language from other scaling frameworks. If an answer choice sounds like it belongs to a different methodology, it probably does. Anchor your reasoning in the Scrum@Scale Guide's own terms.
Domain 2: Patterns of High Performing Teams
Patterns of High Performing Teams
Scrum@Scale starts from the premise that scaling is only as good as the team it scales. Expect scenario questions asking what a single Scrum team needs before you replicate it.
- Reinforce the core Scrum team: Product Owner, Scrum Master, and Developers, working with a shared Sprint cadence.
- Understand what makes a team a healthy unit: clear ownership, a ready backlog, and the ability to deliver a usable increment.
- Recognize signs of a team that is not yet ready to be scaled, such as unclear priorities or chronic impediments.
Questions here tend to be applied rather than definitional: a team is described, and you choose the action that best reflects the pattern. Practice reading the scenario for the underlying dysfunction, not the surface symptom.
Domain 3: Scaling the Teams
Scaling the Teams
This domain covers how individual teams combine into larger structures without breaking the Scrum model.
- Learn how multiple teams coordinate through a Scrum of Scrums rather than a separate management layer.
- Understand how the structure repeats at higher levels, so the same pattern can support larger groups.
- Know why the framework prefers small, cross-functional teams linked by coordination, not a single oversized team.
Think in terms of repetition. The framework's elegance is that the same shape recurs at each level, so if you understand the first level of coordination, you can reason about the next. For a broader walkthrough of how these headings fit together, see the complete guide to all seven RS@SP content areas.
Domain 4: Scrum Master Cycle: Coordinating the "How"
Scrum Master Cycle
The Scrum Master Cycle is concerned with how the work gets done: the delivery side of the organization.
- Focus on removing impediments and improving how teams work, both within and across teams.
- Know that this cycle is about coordination of delivery and continuous improvement, not about directing what to build.
- Be able to distinguish "how" concerns (process, flow, impediments) from "what" concerns (priorities, value).
The cleanest mental shortcut is the label itself: this cycle coordinates the "how." When a scenario describes a cross-team dependency, a blocked integration, or a recurring process problem, you are probably in this cycle's territory.
Domain 5: Product Owner Cycle: Coordinating the "What"
Product Owner Cycle
The Product Owner Cycle mirrors the Scrum Master Cycle but addresses what the organization builds and in what order.
- Focus on alignment of backlog priorities across teams so that teams are not pulling in conflicting directions.
- Understand how a shared vision and coordinated priorities flow down to individual team backlogs.
- Know that this cycle is about value and prioritization, not about how teams execute.
The recurring exam move is to blur the two cycles in a scenario and ask which one owns the problem. If the issue is conflicting priorities or an unclear product direction, think "what." If the issue is a delivery or process breakdown, think "how." A strong grasp of the RS@SP study guide approach helps you drill that distinction.
Domain 6: Connecting the Cycles
Connecting the Cycles
The two cycles do not run in isolation. This domain is about where they meet and why the connection matters.
- Understand that prioritization and delivery must inform each other for the system to function.
- Recognize how decisions in one cycle create constraints or opportunities in the other.
- Be ready for integrated scenarios that require reasoning across both cycles at once.
These are often the hardest questions because no single cycle holds the whole answer. When two answer choices each fix half the problem, look for the option that addresses the interaction between priorities and delivery.
Domain 7: The Credential Itself
The final heading, Registered Scrum@Scale Practitioner Credential, is administrative. It covers the practical mechanics of earning and keeping the credential. Everything in the fees section above belongs here: the course-then-assessment path, the 30-day window, the attempt limit, and the renewal considerations.
The official preparation source is the Registered Scrum@Scale Practitioner Learning Objectives document from Agile Education. Note that the "2020" in its upload path is a file location, not a document version. For a candid view of effort, see how hard the RS@SP exam really is.
Sequencing the Domains Across Four Weeks
Because the assessment follows a course and carries a 30-day window, a compact plan fits best. This is the only schedule in this article; it is organized by domain logic rather than generic technique.
Foundation
- Re-read the Scrum@Scale Guide v2.1 for Domain 1 vocabulary.
- Review Domain 2 patterns while class material is fresh.
Structure
- Work through Domain 3 scaling mechanics.
- Sketch how coordination repeats at each level.
The Two Cycles
- Study Domains 4 and 5 side by side, labeling every example "how" or "what."
- Move on to Domain 6 integration scenarios.
Credential and Finish
- Confirm Domain 7 terms against your ScrumLab account.
- Complete the assessment before the 30-day window closes.
Place the two cycles together deliberately: the contrast between "how" and "what" is easier to hold when studied back to back. When you want realistic repetition, try the practice tests on our main site to find which cycle you confuse most.
Where the Credential Shows Up at Work
The credential is most relevant to people coordinating more than one Scrum team: Scrum Masters, Product Owners, agile coaches, program and release managers, and delivery leaders in organizations that already run Scrum and are growing it. It signals familiarity with a specific scaling approach rather than general agile awareness. We do not publish salary or hiring figures here because none are established in the issuer materials; for qualitative context, explore RS@SP jobs and the RS@SP salary guide, and weigh the investment using the RS@SP ROI analysis.
If you are still orienting, our explainers on what RS@SP certification is and RS@SP training cover the basics, and you can test yourself anytime on the main practice test site.
Frequently Asked Questions
The issuer's published student policy specifies 30 multiple-choice questions with a 75% passing criterion and up to 2 attempts.
According to the issuer policy, sessions are untimed and progress is saved. The 14 live-course hours are an eligibility requirement, not an exam timer. The real deadline is completing the assessment within 30 days after the course ends.
No. Eligibility requires at least 14 hours of live instruction covering the learning objectives with a Registered Scrum@Scale Trainer. The course precedes the ScrumLab assessment.
The issuer policy specifies one-year validity with annual renewal and a brief re-examination at 75%. Some providers describe lifetime validity instead, so confirm the terms on your own ScrumLab account before relying on either claim.
No weights are published. The seven headings come from the learning objectives and are unweighted preparation headings, not an official blueprint, so study all of them rather than guessing at percentages.