Scrum SPS Practice Exam Questions & Answers

7 Free Questions Last reviewed November 13, 2026 Prepared & Reviewed by the ValidExamDumps Editorial Team

40 Practice Questions (Our Bank)
60 minutes Exam Duration
85% Passing Score
USD 250 Official Exam Fee
Exam Facts

Scrum SPS Exam Details

Key details for this exam, checked against the published exam outline

Exam Code
SPS
Full Name
Scaled Professional Scrum
Issuing Body
Scrum.org
Question Format (Our Bank)
Multiple Choice
Delivery
Online
Eligibility
No prerequisites, though attending a Scaled Professional Scrum class is highly recommended
Validity
Does not expire
Practice Questions

Free SPS Practice Questions

Each question shows the correct answer and an explanation of why it is right

VA
ValidExamDumps Editorial Team Every question and its answer is checked by our SPS exam preparation team, who also write the explanation shown with each one. How we research and review these pages

Question 2 Domain 8 Learn how to deliver value across the whole Nexus

Scenario C: Dependencies and Product Backlog items

During Nexus Sprint Planning, representatives from each of the 9-member Scrum Teams

identify many dependencies. This makes it hard for them to choose the work they could pull

into their individual teams for the next Sprint. No matter how they reorganize the Product

Backlog items, they continually find more or new dependencies.

What would you recommend to the two teams that are continually dependent on each other to

help them manage their work?

(choose the best answer)

Correct Answer D
Explanation

The best way to help the two teams that are continually dependent on each other to manage their work is to ensure the appropriate representatives from both teams are present during Cross-Team Refinement. Cross-Team Refinement is an optional event in Nexus that allows the Scrum Teams to collaborate and coordinate on the Product Backlog items that have dependencies or require integration 11. By having the representatives from both teams present during this event, they can identify and resolve the dependencies, clarify the requirements, align the expectations, and plan the work for the next Sprint. This will improve the transparency, the quality, and the value of the Integrated Increment.

The other options are not advisable for the following reasons:

The Nexus Integration Team should not be responsible for integrating the work of these two Scrum Teams, as this would create a bottleneck and a hand-off. The Nexus Integration Team is a specialized Scrum Team that provides services and guidance to the Scrum Teams in the Nexus to ensure that the Integrated Increment is produced every Sprint 11. However, the Nexus Integration Team is not accountable for the integration of the work of the individual Scrum Teams, as this is the responsibility of the Scrum Teams themselves 22.

Reorganizing these two Scrum Teams so that one is responsible for development and one is responsible for integration is not a good idea, as this would create a silo and a separation of concerns. The Scrum Teams in a Nexus should be cross-functional and self-organizing, meaning that they have all the skills and abilities to deliver a potentially releasable product Increment every Sprint 11. Separating the development and the integration tasks would compromise the collaboration, the feedback, and the agility of the Scrum Teams.

Merging the two Scrum Teams together is not a viable solution, as this would create a large and unwieldy team. The Scrum Guide states that the optimal size of a Scrum Team is between three and nine members 33. Merging two Scrum Teams together would exceed this limit and create challenges in communication, coordination, and decision-making. Moreover, merging the two teams would not necessarily eliminate the dependencies, as they may still exist within the larger team or with other teams in the Nexus.

Question 3 Domain 6 Experience the Nexus framework in action

Scenario A: Nexus Sprint Review with Five Scrum Teams

There are five Scrum Teams working on a product. During the Nexus Sprint Review, the teams

present the results of the Sprint. After introductions, each team takes time to present their work

for inspection by individually showing the new features they have built. They are not using a

shared environment. The stakeholders do not provide much feedback. The event ends and

people filter out of the room.

Since teams are not using a shared environment, what is likely?

(choose the best two answers)

Correct Answer C, D
Explanation

According to the Nexus Guide1, the Nexus Sprint Review is an event where the Nexus presents the Done Integrated Increment that was built over the Sprint and collects feedback from the stakeholders. The Integrated Increment is the combined work of all the Scrum Teams in the Nexus that meets the Definition of Done. The Nexus Guide also states that the Nexus Integration Team is a specialized Scrum Team that provides services and guidance to the Scrum Teams in the Nexus to ensure that the Integrated Increment is produced every Sprint.

In the scenario, the teams are not using a shared environment, which implies that they are not integrating their work frequently and effectively. This means that there is no single Integrated Increment that can be inspected and adapted by the stakeholders. This also suggests that the Nexus Integration Team is lacking or nonexistent, or that it is not fulfilling its role of facilitating integration and resolving dependencies. Without a Nexus Integration Team and a shared environment, the Nexus cannot deliver a valuable product Increment that meets the Product Goal.

The Sprint length and the integration phase are not relevant to the scenario. The Sprint length is determined by the Nexus based on the complexity and uncertainty of the product, and it should be less than a month. The integration phase is not a separate phase in Nexus, but a continuous activity that happens throughout the Sprint. Therefore, A and B are not correct answers.

Get the complete SPS question set $20$40

Get Full Access

Question 4 Domain 6 Experience the Nexus framework in action

Currently, your Scrum Teams are organized to address a single functional (component) area of

the product. What should be considered when deciding to move away from such component

teams toward feature teams?

(choose the best three answers)

Correct Answer A, D, E
Explanation

Moving away from component teams toward feature teams is a significant change that should be considered carefully. Here are some of the factors that should be taken into account:

Feature teams have less communication overhead than component teams, as they are able to deliver end-to-end customer features without relying on other teams or components 11. This reduces the complexity and the dependencies among the teams, and improves the transparency and the feedback loop. Feature teams also foster more collaboration and cross-functional learning among the team members, as they have to work on different aspects of the product 22.

When making this change, it helps to have support from the organization, as it may require a shift in the culture, the structure, and the processes of the company 33. The organization should provide the necessary resources, training, and coaching to the teams to help them adopt the feature team model. The organization should also align its goals, incentives, and metrics with the feature team approach, and remove any barriers or impediments that may hinder the teams' performance 44.

Productivity may decrease when making this kind of change, as the teams may face some challenges and difficulties in the transition period 55. For example, the teams may have to learn new skills, technologies, or domains that they are not familiar with. The teams may also have to deal with legacy code, technical debt, or integration issues that may slow down their delivery. The teams may also experience some resistance or conflict from the existing component teams or stakeholders. Therefore, the teams should expect some temporary setbacks and losses in productivity, and focus on continuous improvement and adaptation.

The other options are not correct for the following reasons:

With feature teams, it is not easier to calculate the productivity per team, as productivity is not a simple or straightforward metric to measure in software development [6]. Productivity depends on various factors, such as the quality, the value, the complexity, and the customer satisfaction of the product. Moreover, focusing on the productivity per team may create a competitive or individualistic mindset among the teams, rather than a collaborative or collective one. The teams should focus on delivering the best possible product Increment that meets the Product Goal and the Definition of Done, rather than on maximizing their productivity [7].

You can do Scrum without feature teams, as Scrum does not prescribe any specific team structure or organization [8]. Scrum only requires that the Scrum Team is cross-functional, self-organizing, and accountable for delivering a potentially releasable product Increment every Sprint [9]. However, feature teams are generally more aligned with the Scrum values and principles, as they enable the teams to deliver customer-centric features faster and more frequently, and to respond to changes more effectively [10]. Therefore, feature teams are recommended, but not mandatory, for Scrum.

Question 5 Domain 4 Identify, visualize, minimize and remove dependencie

The purpose of a Nexus Sprint Retrospective is to:

(choose the best two answers)

Correct Answer A, C
Explanation

The Nexus Sprint Retrospective is an event that occurs at the end of the Sprint where the Nexus, which is a group of approximately three to nine Scrum Teams working on the same product, plans ways to increase quality and effectiveness across the whole Nexus 11. The purpose of the Nexus Sprint Retrospective is to inspect and adapt the Nexus framework, the integrated work, the processes, the tools, and the interactions among the Scrum Teams 11. Therefore, statement C is correct.

The Nexus Sprint Retrospective follows a three-step process: first, representatives from each Scrum Team identify issues that affect multiple teams; second, each Scrum Team conducts its own Sprint Retrospective; and third, representatives from each team meet again to discuss any actions needed based on the shared challenges 112233. The Nexus Sprint Retrospective enables bottom-up intelligence to improve how the Scrum Teams in a Nexus are working together, as it allows the teams to share their insights, learn from each other, and collaborate on solutions 44. Therefore, statement A is also correct.

Statement B is incorrect because the Nexus Sprint Retrospective is not a forum for management to see how the Nexus is performing, but rather a time for the Nexus to self-organize and self-improve 1144. Statement D is incorrect because the Nexus Sprint Retrospective is not a single meeting to inspect and adapt how all Scrum Teams work together, but rather a combination of three meetings that involve both individual and collective reflection and action 112233.

Question 7 Domain 8 Learn how to deliver value across the whole Nexus

The purpose of the Nexus Sprint Backlog is:

(choose the best two answers)

Correct Answer B, D
Study Guide

What the Scrum SPS Exam Covers

Exam domains verified against the Official Scrum SPS exam guide, last checked November 2026.

Domain 1 Identify typical challenges

Understand the common obstacles organizations face when scaling beyond a single team. Learn strategies to recognize and overcome these challenges while maintaining Scrum principles and delivering value at scale.

Domain 2 Understand how to find the scale that works

Explore how to identify the right scale for your organization and expand what works best. This includes understanding when and how to scale down or de-scale practices that no longer serve your goals.

Domain 3 The negative impact of cross-team dependencies

Examine how dependencies between teams can disrupt value delivery. Learn why these dependencies form and what their effects are on product development and team performance.

Domain 4 Identify, visualize, minimize and remove dependencie

Develop practical skills in finding and displaying dependencies across teams. Use cross-team refinement and other techniques to reduce and eliminate dependencies that slow down delivery.

Sample question from this domain above Q5

Domain 5 Learn how the Nexus framework extends

Understand how the Nexus framework builds on core Scrum rules to enable scaling. Discover how it reinforces Scrum's principles and artifacts while adding new structures to support multiple teams.

Domain 6 Experience the Nexus framework in action

See how Nexus events, artifacts and accountabilities work in practice. Learn about the Nexus Integration Team role and how the framework's mechanics support teams in delivering integrated products.

Sample questions from this domain above Q1Q3Q4

Domain 7 Experience techniques for organizing teams

Discover strategies for structuring teams within scaled organizations. Understand how to organize work and coordinate efforts across a Nexus while maintaining autonomy and focus.

Sample question from this domain above Q6

Domain 8 Learn how to deliver value across the whole Nexus

Focus on ensuring value flows through the entire scaled organization, not just individual teams. Learn how to align and coordinate work so each team contributes to overall product success.

Sample questions from this domain above Q2Q7

FAQ

SPS Exam FAQ

Common questions about the exam itself

What background do I need to take the SPS exam?
There are no formal prerequisites. However, Scrum.org strongly recommends attending the Scaled Professional Scrum course because the exam tests understanding of the Nexus Framework and scaling practices that are covered in depth during training. Some candidates do pass without the course if they have several years of Scrum experience and study the Nexus Framework independently.
How hard is the SPS exam compared to PSM exams?
SPS is classified as an intermediate-level assessment, sitting between PSM I and PSM II in difficulty. It requires understanding of scaling concepts and the Nexus Framework rather than just core Scrum knowledge. Questions ask you to apply scaling principles to complex real-world situations, not just recall facts.
What is the passing score for SPS?
You must score at least 85 percent to pass the SPS exam. This same threshold applies whether you take the exam once or retake it after an initial failure.
How long does the SPS exam take?
The exam duration is not published on Scrum.org's official certification page. Contact Scrum.org support for the exact testing time.
How much does the SPS exam cost?
The SPS exam costs USD 250 per attempt. If you attend an official Scaled Professional Scrum course, you receive one free attempt as part of the training. Each additional attempt costs the full 250 dollar fee.
What is the retake policy for SPS?
If you attend an SPS course and attempt the exam within 14 days of receiving your password but score below 85 percent, you get a free second attempt. Outside of a course, each retake costs the full 250 dollar exam fee.
Does the SPS certification expire?
No. The Scaled Professional Scrum certification does not expire and requires no renewal. Once you pass the exam, your credential remains valid for life.
How do I take the SPS exam?
The SPS exam is taken online. You need an internet connection, a computer with a webcam, and a valid password to access the exam through Scrum.org's platform. Many people also use the Google Translate Plugin to take the test in their native language, though Scrum.org does not guarantee translation quality.
How long should I study to prepare for SPS?
The two or three day Scaled Professional Scrum course includes over 50 practices and an experiential simulation of scaling work across teams. Most candidates who take the course feel reasonably prepared, though additional self-study is often helpful. Candidates without the course should expect to spend considerably more time learning the Nexus Framework independently.
Where does SPS fit in the Scrum.org certification path?
SPS is positioned as an intermediate-level certification for people who already understand core Scrum and want to develop expertise in scaling. It focuses specifically on the Nexus Framework, unlike PSM certifications which test general Scrum mastery. You do not need to hold any other Scrum.org certification before taking SPS.

Other Scrum Exams

Free practice questions for more Scrum certification exams

All Scrum exams