- How to Read the Seven Domains
- 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
- Domain Comparison at a Glance
- Sequencing Your Prep by Domain
- Frequently Asked Questions
- The seven domains are headings from Scrum Inc.'s Learning Objectives (updated March 2025), not an officially weighted exam blueprint.
- Domains 4 and 5 are the two cycles; Domain 6 tests how they connect, so study them together.
- Eligibility requires at least 14 hours of live instruction with a Registered Scrum@Scale Trainer.
- The ScrumLab assessment is 30 multiple-choice questions, a 75% passing criterion, up to 2 attempts, within 30 days of course end.
How to Read the Seven Domains
The Registered Scrum@Scale Practitioner credential is issued through Agile Education by Scrum Inc. Its preparation material is organized into seven top-level headings in the official Registered Scrum@Scale Practitioner Learning Objectives document, updated March 2025. Those headings form the spine of this guide.
One point deserves emphasis before anything else: the seven headings are unweighted preparation-curriculum headings. They are not an official seven-domain exam blueprint with published percentages, and they do not establish exhaustive examination coverage. Any site that hands you a neat "Domain 3 is 18% of the exam" table for this credential is inventing precision the issuer has not published. This guide treats the domains as a map of what your instructor must cover and what you should be able to explain, not as a scoring formula.
It is also worth being clear about scope. This guide concerns the Scrum@Scale practitioner credential from Scrum Inc. It is not SAFe, not a Scrum.org or Nexus examination, and not the RSM or RS@SF credentials. The vocabulary of Scrum@Scale (Scrum Master Cycle, Product Owner Cycle, Executive Action Team, Scrum of Scrums) is its own, and the questions use it. For a broader orientation to the credential, see What Is RS@SP? and the RS@SP Certification overview.
Domain 1: The Scrum@Scale Framework
The first domain establishes what Scrum@Scale is and why it exists. Expect your trainer to open here, and expect the assessment to check that you can describe the framework in your own words rather than recite slogans.
Domain 1: The Scrum@Scale Framework
The foundation: what the framework is for, how it is structured, and how it differs from the single-team Scrum you already know.
- Scrum@Scale as a way to extend Scrum beyond a single team by linking teams into a network rather than a hierarchy
- The idea of a minimum viable bureaucracy: coordinating only as much as needed
- The two cycles that organize the framework, the Scrum Master Cycle and the Product Owner Cycle
- The role of the framework's components in making the organization responsive and able to deliver value continuously
- How the framework builds on the core Scrum values and empirical process control
A common trap here is treating Scrum@Scale as "Scrum with more meetings." The framework is deliberately modular: you scale the parts that need scaling. Questions in this area tend to reward candidates who understand the reasoning behind the structure, such as why coordination is decomposed into a "how" cycle and a "what" cycle, instead of those who memorized a diagram.
Domain 2: Patterns of High Performing Teams
Scaling a bad team multiplies the problem. That is why the Learning Objectives devote an entire heading to what makes individual Scrum teams effective before discussing how to link them.
Domain 2: Patterns of High Performing Teams
The team-level patterns that make scaling worthwhile. This domain is where your existing Scrum knowledge gets tested against Scrum@Scale's expectations.
- The characteristics of high performing teams and the patterns that produce them
- Team-level practices around ownership, autonomy, and continuous improvement
- Why healthy teams are a prerequisite for effective scaling
- Connecting team-level behavior to the outcomes the wider organization needs
Candidates who come from a strong Scrum background sometimes underestimate this domain because it feels familiar. The risk is answering from personal experience instead of from the framework's stated patterns. When a question describes a team problem, ask what pattern from your course material it maps to, not what you did at your last company.
Domain 3: Scaling the Teams
This is where the framework's signature structures appear. Domain 3 covers how multiple teams are grouped and coordinated so that they behave like a single, larger, effective unit.
Domain 3: Scaling the Teams
How teams of teams are formed and how they stay aligned without heavy top-down control.
- Scrum of Scrums as the mechanism for coordinating a group of teams
- How the pattern repeats: a Scrum of Scrums of Scrums when more scale is required
- The roles that emerge at each level to coordinate delivery and prioritization
- Why the structure is fractal, using the same pattern at every level
The fractal idea is worth internalizing, because it makes many questions easier. If you understand that the pattern at the team-of-teams level mirrors the pattern at the team level, you can reason through unfamiliar scenarios instead of hunting for a memorized fact. Candidates should also be comfortable with how this domain feeds the next two, since the coordination roles it introduces own the cycles that follow.
Domain 4: Scrum Master Cycle: Coordinating the "How"
Domain 4 is the first of the two cycles at the heart of the framework. The Scrum Master Cycle is concerned with how the work gets done: delivery, impediments, and continuous improvement across the network of teams.
Domain 4: Scrum Master Cycle: Coordinating the "How"
The cycle that keeps delivery flowing and removes obstacles at scale.
- The purpose of the cycle: coordinating execution across teams
- Handling impediments that a single team cannot resolve alone
- Continuous improvement and how it propagates through the organization
- Cross-team dependencies and how they are surfaced and managed
- The role of the Scrum Master function at scale and its relationship to the Executive Action Team
Questions here often present a scenario, such as an impediment that crosses team boundaries, and ask which part of the cycle handles it or who should act. Practice by taking any impediment and tracing where it escalates. If it cannot be solved at the team level, which structure picks it up? That mental routing exercise is more valuable than rereading definitions.
Domain 5: Product Owner Cycle: Coordinating the "What"
The mirror image of Domain 4, the Product Owner Cycle governs what the teams build: strategy, prioritization, and the backlog structure that aligns many teams to a shared direction.
Domain 5: Product Owner Cycle: Coordinating the "What"
The cycle that aligns product direction and prioritization across the whole network of teams.
- The purpose of the cycle: coordinating vision, strategy, and priorities
- The relationship between a strategic vision and the backlogs that serve it
- The coordinating product ownership roles and how they connect to team-level Product Owners
- Backlog prioritization and refinement across multiple teams
- Ensuring teams are building something coherent, not a collection of disconnected features
Candidates frequently confuse the two cycles under exam pressure. A reliable discriminator: if the scenario is about removing a blocker or improving how work flows, think Scrum Master Cycle; if it is about deciding what is most valuable or aligning on direction, think Product Owner Cycle. That one distinction resolves a large share of ambiguous-looking items.
Domain 6: Connecting the Cycles
Domain 6 is where the framework's two halves meet. A Scrum Master Cycle that delivers efficiently but builds the wrong thing is waste, and a Product Owner Cycle with a brilliant strategy but broken delivery goes nowhere. The framework ties them together, and the Learning Objectives give that integration its own heading.
Domain 6: Connecting the Cycles
How the Scrum Master Cycle and Product Owner Cycle interact so that delivery and direction stay aligned.
- The points where the two cycles intersect and exchange information
- How feedback from delivery informs prioritization, and how priorities shape delivery
- The role of the leadership structures that keep both cycles in balance
- Why neither cycle can succeed without the other
Integration questions tend to be scenario-driven and reward holistic thinking. When a scenario describes a symptom, like teams delivering consistently but stakeholders being unhappy with outcomes, consider which cycle is out of alignment and how the connecting mechanisms should surface it.
Domain 7: The Credential Itself
The seventh heading is unusual: it is administrative rather than conceptual. Domain 7, "Registered Scrum@Scale Practitioner Credential," covers the credential's own terms. It is retained in the Learning Objectives alongside the six framework domains, so candidates should be ready for it.
Domain 7: Registered Scrum@Scale Practitioner Credential
The facts of how the credential is earned and maintained, drawn from the issuer's published policy.
- Eligibility: at least 14 hours of live instruction covering the objectives, delivered by a Registered Scrum@Scale Trainer
- The assessment: administered online by Scrum Inc. through ScrumLab
- The published student policy: 30 multiple-choice questions, a 75% passing criterion, up to 2 attempts, completion within 30 days after the course ends
- Sessions are untimed and progress is saved, so the live-course hours are not an exam timer
- The issuer policy specifies one-year validity and an annual renewal with a brief re-examination (75% required, up to 2 attempts)
The details of eligibility and process are covered more fully in RS@SP Requirements 2026: Eligibility, Prerequisites & How to Qualify, and the scoring threshold is unpacked in RS@SP Passing Score 2026. For timing logistics, see RS@SP Exam Dates 2026.
Fees and renewal: what is and is not settled
Cost questions need care. Course tuition is set by the individual trainer, so it varies. The issuer's policy describes a $50 USD per-student credentialing charge for legal residents of the top 100 GDP-per-capita countries, or $25 elsewhere, but that charge is billed to trainers, not presented as a universal standalone candidate exam price. In practice, most candidates encounter the credential as part of a trainer's course price.
Renewal is the area where published statements conflict. The same issuer policy specifies annual renewal at the $50/$25 residence tier plus a brief re-examination. However, some training providers describe annual renewal on their own FAQ pages while others describe the credential as lifetime. Those provider claims do not override the issuer policy, so confirm current account-specific ScrumLab terms before assuming any particular renewal fee or validity period. The full pricing picture is in RS@SP Certification Cost 2026.
Domain Comparison at a Glance
The table below summarizes what each domain asks of you. Note that there is no weighting column, because the issuer has not published one.
| Domain | Nature | What to be able to do |
|---|---|---|
| 1. The Scrum@Scale Framework | Conceptual foundation | Explain the framework's purpose and structure in your own words |
| 2. Patterns of High Performing Teams | Team-level practice | Map team scenarios to named patterns |
| 3. Scaling the Teams | Structural | Describe Scrum of Scrums and the repeating pattern |
| 4. Scrum Master Cycle | Process: "how" | Route impediments and improvements to the right structure |
| 5. Product Owner Cycle | Process: "what" | Align strategy, priorities, and backlogs |
| 6. Connecting the Cycles | Integration | Diagnose misalignment between delivery and direction |
| 7. RS@SP Credential | Administrative | Recall eligibility, assessment format, and renewal terms |
Sequencing Your Prep by Domain
Because the domains build on each other, order matters more than total hours. The plan below assumes you have already attended the live course, since the 14-hour instruction requirement comes first, and are now preparing for the ScrumLab assessment inside the 30-day completion window. Compress or stretch it to fit, but keep the sequence.
Foundations: Domains 1 and 2
- Rewrite the framework's purpose and structure from memory
- List the team patterns from your course and tie each to a scenario
Structure and cycles: Domains 3, 4, and 5
- Draw the Scrum of Scrums repeating pattern at two and three levels
- Study the Scrum Master Cycle and Product Owner Cycle back to back
- Practice the "how versus what" discrimination on sample scenarios
Integration and credential: Domains 6 and 7
- Work through scenarios where delivery and direction are misaligned
- Memorize the assessment format, passing criterion, attempts, and renewal terms
Leave time at the end for timed-style practice with scenario questions, since the assessment itself is untimed but you should be fluent before you sit it. With only 2 attempts available, it is worth arriving prepared rather than treating the first try as a diagnostic. For a fuller preparation framework, read the RS@SP Study Guide 2026, and keep the RS@SP Cheat Sheet handy for last-minute review. You can also pressure-test your recall with the practice questions on the main practice test site.
Key Takeaway
Do not allocate study time by an imagined domain weighting. Spread your effort so that you can explain every domain, and spend extra time where the cycles blur together, since Domains 4, 5, and 6 are where candidates most often lose points on scenario items.
Where the Domains Fit in Your Decision
Understanding the domains also helps you judge whether the credential suits your goals. The content is oriented toward people coordinating multiple teams: Scrum Masters, Product Owners, agile coaches, and managers working at scale. If you are weighing whether it is worth the investment, Is the RS@SP Certification Worth It? walks through the reasoning, and How Hard Is the RS@SP Exam? addresses difficulty. For career context, see RS@SP Jobs and the qualitative picture in the RS@SP Salary Guide. A broader look at the pass-rate question is in RS@SP Pass Rate 2026: What the Data Shows.
Frequently Asked Questions
No official weighting is published. The seven headings come from the Learning Objectives document and are unweighted preparation-curriculum headings, not an exam blueprint with percentages. Prepare to explain all seven rather than optimizing around a guessed distribution.
The issuer's published student policy specifies 30 multiple-choice questions with a 75% passing criterion. You get up to 2 attempts, and you must complete the assessment within 30 days after the course ends. Sessions are untimed and progress is saved.
Yes. Eligibility requires at least 14 hours of live instruction covering the Learning Objectives with a Registered Scrum@Scale Trainer. The assessment is administered online by Scrum Inc. through ScrumLab after that course.
One trainer describes the delivery as open-book, but that is a provider's description rather than a rule confirmed in the issuer's policy. Prepare as though you must know the material, because scenario questions are hard to answer by lookup alone.
The issuer policy specifies one-year validity with annual renewal at a $50 or $25 residence-tier charge and a brief re-examination requiring 75%. Some providers describe the credential differently, so confirm current account-specific ScrumLab terms before relying on any universal fee or validity claim.