SPS Exam Guide: What to Study, How to Prepare, and How to Plan Your Attempt
The Scaled Professional Scrum (SPS) certification validates knowledge of Scrum.org’s Nexus Framework and its use for helping multiple Scrum Teams work from one Product Backlog and create an Integrated Increment that meets a goal. It is suited to practitioners involved in scaling Scrum, including people working across product, delivery, facilitation, and team-coordination responsibilities. This guide helps you decide whether independent preparation is sufficient, whether the official course is worthwhile, and when you are ready to use an assessment attempt.
What the SPS certification validates
SPS validates your understanding of how Nexus supports several Scrum Teams working toward one product goal, rather than testing generic familiarity with Agile vocabulary. The central capability is connecting team-level Scrum work with the coordination, integration, and transparency needed to produce one Integrated Increment.
Scrum.org identifies the Scaled Professional Scrum certification with the Nexus Framework. The assessment is intended to verify knowledge of using that framework to enable multiple Scrum Teams to work from one Product Backlog and build an Integrated Increment that meets a goal. That scope matters: studying isolated Scrum practices without understanding their relationship across teams leaves a major gap.
A useful way to interpret the certification is as a coordination exam. You need to understand how a scaled product-development effort is organized, how dependencies and integration concerns become visible, and how the Nexus approach relates to the Scrum Teams and product work involved. The goal is not to memorize labels detached from their purpose.
The official course describes its subject as launching, structuring, organizing, and managing a large Agile project using Scrum. That description points toward practical application. When you study a framework element, ask what problem it addresses, which participants use it, and how it contributes to an Integrated Increment. Those questions are more productive than collecting definitions alone.
Who should consider SPS
SPS is most relevant to people who must understand or support Scrum across multiple teams working on one product. It can serve practitioners who coordinate delivery, facilitate scaled events, guide product work, or need a shared framework for discussing integration and cross-team dependencies.
The evidence supplied for the certification does not define a formal professional prerequisite or restrict the assessment to a particular job title. Scrum.org states that attending a Scaled Professional Scrum class is highly recommended, but it is not a prerequisite for taking the SPS assessment. That leaves candidates with a preparation choice rather than a mandatory training gate.
Choose independent study when you already understand Scrum, can read the official Nexus material critically, and can explain how several teams contribute to one integrated outcome. Choose the course when you need structured practice, instructor clarification, or a realistic setting in which to work through scaled coordination problems.
The course uses a Nexus simulation in which participants organize and simulate a scaled product-development project. That activity can be particularly useful if your experience is limited to one Scrum Team. It gives you a way to test whether you can apply the framework to coordination and integration situations, not merely repeat terminology.
Do not treat a job title as proof of readiness. A Scrum Master, Product Owner, manager, developer, consultant, or delivery leader may all have relevant reasons to pursue SPS, but each person should assess their actual exposure to multi-team product work. If your Scrum fundamentals are weak, address that gap before concentrating on Nexus-specific details.
What the assessment covers
The SPS assessment covers three named focus areas: the Nexus Framework, Nexus scaling fundamentals, and translation. Prepare across all three rather than assuming that knowledge of the framework structure alone will be enough.
The Nexus Framework area should be studied as a connected system. Learn the purpose of its elements, how they relate to Scrum Teams, and how they support a common product direction. The objective is to recognize appropriate framework behavior in context, not just identify a term when it appears in isolation.
Nexus scaling fundamentals require attention to the problems created when multiple teams work on one product. Study integration, dependencies, shared visibility, and the conditions needed for teams to create an Integrated Increment. Keep asking what changes when the number of collaborating teams increases and why a framework element exists.
Translation is best approached as application. A question in this area may require you to translate a framework principle into a practical response to a coordination or product-development situation. Build the habit of explaining what a concept would mean in team behavior, planning, integration, or inspection rather than limiting your notes to abstract wording.
The supplied official facts do not provide percentage weights for these focus areas. Do not invent a weighting model or prioritize one area based on an unofficial chart. Use the three named areas as a complete study boundary, then spend additional time wherever practice questions or self-explanation reveal uncertainty.
Assessment facts that affect your plan
The SPS assessment contains 40 questions, has a 60-minute time limit, and requires a passing score of 85%. It uses multiple-choice, multiple-answer, and true/false formats. Those facts make careful reading and answer selection as important as broad content coverage.
The required passing score is 85%, so a candidate should not plan around recognizing a few familiar terms. A safer preparation standard is consistent, reasoned performance across mixed question formats. You need enough understanding to reject attractive but incomplete answers, especially when more than one answer may be correct.
A 60-minute time limit means you should practice moving forward when a question becomes unproductive. This is a preparation recommendation, not an official timing rule: read the complete prompt, identify whether it asks for one answer or multiple answers, eliminate options that conflict with the framework, and return to difficult items if the assessment interface permits it.
The assessment is offered in English. Scrum.org states that candidates may use the Google Translate plugin under its specified instructions. Review the official assessment page for the applicable instructions before relying on that option, and do not assume that translation support changes the need to understand the framework’s terminology.
The assessment costs $250 USD per attempt. Include that cost in your scheduling decision, particularly because an assessment password does not expire but is valid for one attempt only. Avoid buying or using an attempt simply because you have finished reading; set a readiness threshold based on your practice performance and ability to explain the material.
The certification is lifetime-valid and does not require an annual renewal fee. It also includes a free Credly digital credential. These are administrative outcomes of certification, not substitutes for preparation, but they may matter when you compare the credential’s long-term maintenance requirements with your professional plans.
Should you take the official course?
The official Scaled Professional Scrum with Nexus course is a strong option when you want activity-based preparation and guided practice with scaling challenges. It is not compulsory: Scrum.org recommends attending the class, but attendance is not a prerequisite for taking the SPS assessment.
The course is described as activity-based training designed to develop skills for overcoming challenges when scaling Scrum. Its Nexus simulation has a practical advantage because it asks participants to organize and simulate a scaled product-development project. That experience can expose misunderstandings that are easy to miss while reading.
The official course includes a free attempt at the SPS certification assessment. Confirm the current course terms and scheduling details on the official course page before enrolling, because the value of a course depends not only on the included attempt but also on your need for instruction, practice, and discussion.
Independent preparation may be the better decision if you already work with several teams, can study the official framework material carefully, and have a reliable way to test your reasoning. A class is not automatically the right choice for every candidate. The useful question is whether structured simulation and instructor feedback will close gaps that self-study would leave open.
If you attend a class, do not treat the included attempt as an automatic final step. Use the training activities to identify weak concepts, review the official assessment guidance, and schedule the attempt only after you can explain the framework without relying on class notes or memorized phrases.
Build a source-first study sequence
Start with the official assessment page to establish the scope, formats, passing requirement, language information, and attempt conditions. Then study the official Nexus course description for the practical emphasis on launching, structuring, organizing, and managing a large Scrum-based Agile project. Use those sources as the boundary for your preparation.
First, map the three named focus areas into a study checklist: Nexus Framework, Nexus scaling fundamentals, and translation. Under each heading, write questions you must be able to answer. For example: what is the purpose of a framework element, what scaling problem does it address, and how would its use affect coordination or integration?
Second, read the relevant official Nexus material slowly and create a relationship map. Put the product goal, Product Backlog, Scrum Teams, coordination mechanisms, and Integrated Increment into one diagram. The diagram is not a replacement for the source; it is a way to expose whether you understand how the parts work together.
Third, apply each concept to a neutral scenario. Imagine multiple teams contributing to one product while facing dependency or integration risk. Explain what should become visible, what conversations need to occur, and how the desired integrated outcome remains connected to the product goal. Keep the exercise conceptual and framework-based rather than trying to predict live assessment questions.
Fourth, test recall without notes. Define a term, explain its purpose, and describe what would go wrong if it were ignored. If you can repeat a definition but cannot explain its consequence in a multi-team setting, mark that topic for another study cycle.
Finally, review assessment mechanics and your administrative plan. Confirm the current official instructions, language support conditions, password status, and any scheduling information before using an attempt. The research supplied here establishes the key facts above, but candidates should use the official pages for current operational instructions.
Use a practical four-phase roadmap
A four-phase roadmap keeps preparation focused: establish Scrum and Nexus foundations, connect the scaling model, practice translation, then verify readiness. The phases need not have fixed calendar lengths; increase or reduce study time according to your prior experience and the weaknesses revealed by self-testing.
Phase one is foundation building. Read the official material and write a plain-language explanation of the SPS purpose. Your explanation should include multiple Scrum Teams, one Product Backlog, and an Integrated Increment that meets a goal. If any of those relationships feels unclear, do not move on simply because the vocabulary looks familiar.
Phase two is system mapping. Study the Nexus Framework as an arrangement of responsibilities, interactions, and integration concerns rather than as a list. Draw how work moves from shared product direction through team activity toward an Integrated Increment. Then challenge your diagram: where could dependencies be hidden, where could integration risk emerge, and what information would help people inspect the product work?
Phase three is translation practice. Take a principle or framework element and convert it into a response to a situation. For instance, if several teams are contributing to one product and discover that their work does not combine cleanly, explain the framework-oriented concern and the type of coordination or inspection that should follow. Do not invent a proprietary procedure and present it as an official requirement.
Phase four is readiness verification. Mix multiple-choice, multiple-answer, and true/false practice from legitimate study material. For every missed answer, record the underlying concept, why your choice was tempting, and what evidence supports the correct reasoning. Schedule the assessment only when your performance is stable and you can justify answers without guessing.
A candidate who is new to scaled Scrum may need more time in phases one and two. Someone with practical multi-team experience may need more translation and assessment-format practice. The roadmap is a recommendation; the official sources do not prescribe a required study schedule.
How to study multiple-answer and scenario questions
Treat multiple-answer questions as a completeness test, not a faster version of multiple-choice. Read the prompt for its exact scope, evaluate every option independently, and select only choices supported by the framework and the situation described.
For multiple-choice items, identify the decision being tested before examining the distractors in detail. Ask whether the question is about purpose, structure, scaling behavior, integration, or application. Then remove options that solve a different problem, introduce an unsupported assumption, or describe isolated team behavior when the question concerns multiple teams.
For true/false items, be alert to absolute wording and hidden changes in scope. A statement may sound compatible with Scrum while contradicting the Nexus context or the goal of an Integrated Increment. Check each clause rather than deciding from one familiar phrase.
Scenario practice should be deliberately modest. Use hypothetical product-development situations to test reasoning, but do not claim that your scenario reproduces the assessment. The purpose is to rehearse applying concepts, recognizing dependencies, and explaining why integration and shared product direction matter.
After each practice set, classify errors. A terminology error calls for rereading. A framework-relationship error calls for a diagram or explanation from memory. A question-reading error calls for slower parsing of the prompt and answer instructions. A guessing error means your readiness threshold is not yet met, even if the final score happened to be acceptable.
Common preparation mistakes to avoid
The most damaging mistake is studying generic Scrum content while neglecting the multi-team integration problem that defines SPS. Scrum knowledge is useful foundation, but it does not by itself demonstrate understanding of how Nexus supports multiple teams working from one Product Backlog.
Another mistake is memorizing framework names without learning their purpose. For each term, write the problem it addresses, the participants affected, and the outcome it supports. If you cannot connect the term to coordination, transparency, integration, or the shared product goal, return to the source material.
Do not assume that attending the course removes the need for individual review. The simulation can reveal practical issues, but the assessment still requires independent reading, careful answer selection, and familiarity with the official scope.
Do not use unofficial dumps or leaked-question claims as a preparation strategy. They are not a substitute for understanding the Nexus Framework, may be inaccurate or unauthorized, and cannot guarantee a passing result. Prepare from official material and use legitimate practice only to improve reasoning and recall.
Avoid spending all your time on administrative facts while leaving translation weak. Knowing that the assessment has 40 questions and a 60-minute time limit helps planning, but those facts do not replace the ability to apply the framework to a scaled product-development situation.
Finally, do not book an attempt merely because a password does not expire. The password is valid for one attempt only, so the absence of an expiration date is not a reason to rush. Use the extra flexibility to prepare properly and confirm the current official instructions before scheduling.
Decide when you are ready
You are ready to consider an attempt when you can explain the SPS purpose, connect the three official focus areas, reason through multi-team integration situations, and handle all listed question formats without relying on recognition alone. Your decision should be based on demonstrated understanding, not on the number of study hours completed.
Use a readiness review with four checks. First, explain how multiple Scrum Teams can work from one Product Backlog and contribute to an Integrated Increment that meets a goal. Second, describe the Nexus Framework and scaling fundamentals in your own words. Third, translate framework ideas into responses to neutral scenarios. Fourth, complete mixed practice while recording why each answer is correct.
Pay special attention to uncertainty rather than only wrong answers. If you reached a correct answer by elimination or intuition, treat that item as provisional and investigate the concept. An 85% passing requirement leaves little room for careless assumptions, particularly when a question uses a format you have not practiced.
Review your language plan before the attempt. The assessment is offered in English, and Google Translate may be used under Scrum.org’s specified instructions. Confirm those instructions on the official assessment page and make sure your planned approach is permitted before you begin.
Make the final administrative check close to scheduling: confirm the current price, assessment access instructions, password conditions, language guidance, and any course-related terms directly on Scrum.org. The supplied official research establishes $250 USD per attempt, but time-sensitive operational details should always be checked at the source.
Plan the attempt and the next step
Plan one focused assessment session rather than treating the attempt as an experiment. Have your study notes closed unless the official assessment instructions explicitly allow a particular aid, understand the question formats, and use the available time to read every prompt carefully.
Because the assessment has a 60-minute time limit and contains 40 questions, pace yourself without turning the session into a race. This is a practical recommendation: answer questions you understand, flag uncertainty where the interface allows it, and revisit difficult items with attention to whether the question asks for one answer or more than one.
If you pass, record the certification information and claim the free Credly digital credential if you want to use it. The certification is lifetime-valid and does not require an annual renewal fee, so your follow-up can focus on applying the framework responsibly rather than planning a renewal cycle.
If you do not pass, avoid reconstructing supposed live questions or relying on memory-based claims from other candidates. Review the official scope, identify which focus area or reasoning pattern caused difficulty, and rebuild your study plan around that gap before using another attempt. An assessment result should guide learning, not encourage question memorization.
If you are still deciding whether to enroll in training, compare your gap with what the course offers: activity-based learning, a Nexus simulation, and a free attempt at the SPS certification assessment. If your gap is mainly terminology and reading discipline, self-study may be sufficient; if it is applying scaled coordination concepts, structured practice may provide greater value.
Official references and a final checklist
Use the official assessment page for certification scope, assessment mechanics, attempt conditions, language information, price, and credential details. Use the official course page to evaluate the activity-based training, Nexus simulation, and included free assessment attempt. These sources should remain your authority for changes to operational information.
Before scheduling, confirm that you can do the following: explain the certification’s purpose; distinguish team-level Scrum knowledge from Nexus scaling knowledge; connect the Nexus Framework, scaling fundamentals, and translation focus areas; reason about one Product Backlog and an Integrated Increment; practice multiple-choice, multiple-answer, and true/false items; and justify answers without relying on dumps.
Then confirm the practical details: the assessment is in English; Google Translate use follows Scrum.org’s specified instructions; the assessment costs $250 USD per attempt; the passing score is 85%; the time limit is 60 minutes; and the assessment contains 40 questions. Recheck the official page before acting because administrative instructions can change.
The most useful next action is to create a gap list from the official scope and start with the concept you cannot yet explain clearly. Read, map, apply, test, and review in that order. That sequence turns preparation from passive content collection into evidence that you can reason about Scrum at Nexus scale.
Conclusion
SPS preparation should culminate in a practical judgment: can you explain and apply Nexus concepts when multiple Scrum Teams must create one integrated product outcome? The official course is recommended but optional, while independent study is viable when it includes source-based reading, scenario reasoning, and mixed-format practice. Confirm the current official instructions, use your one-attempt password deliberately, and schedule only after your understanding is consistent across the Nexus Framework, scaling fundamentals, and translation focus areas.
