Scrum SPS Practice Exam Questions & Answers
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
- Full Question Set
- 40 questions Get All Questions
Free SPS Practice Questions
Each question shows the correct answer and an explanation of why it is right
Question 1 Domain 6 Experience the Nexus framework in action
True or False: When multiple Scrum Teams are working together on the same product, each
team should maintain a separate Product Backlog.
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)
The other options are not advisable for the following reasons:
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)
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
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)
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:
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)
Question 6 Domain 7 Experience techniques for organizing teams
True or False: A Nexus Integration Team is responsible for actually doing the integration work
during the Sprint.
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)
The other answers are not correct for the following reasons:
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.
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
SPS Exam FAQ
Common questions about the exam itself
What background do I need to take the SPS exam?
How hard is the SPS exam compared to PSM exams?
What is the passing score for SPS?
How long does the SPS exam take?
How much does the SPS exam cost?
What is the retake policy for SPS?
Does the SPS certification expire?
How do I take the SPS exam?
How long should I study to prepare for SPS?
Where does SPS fit in the Scrum.org certification path?
Other Scrum Exams
Free practice questions for more Scrum certification exams
