Scrum SPS Practice Exam Questions & Answers
6 Free Questions
· Last reviewed: October 1, 2026
· Prepared & Reviewed by the ValidExamDumps Editorial Team
Exam Facts
Scrum SPS Exam Details
Key details for this exam, checked against the published exam outline
40
Practice Questions (Our Bank)
60 minutes
Exam Duration
85%
Passing Score
USD 250
Official Exam Fee
- 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
Scenario B: Six Team Nexus with complex dependencies
A six team Nexus is developing a complex product, with different parts of the product that only
certain Scrum Teams can work on. In fact, there are some highly specialized individuals outside
the Nexus that are required for some of the work. In past Sprints the Nexus encountered
challenges dealing with the many dependencies between Scrum Teams.
Which of the following two strategies would be most effective in dealing with their
dependencies?
(choose the best two answers)
Correct Answer:
A, C
Explanation
The Nexus framework is a way of scaling Scrum for multiple teams working on a single product. The Nexus framework uses Scrum as its building block and extends it only where necessary to minimize and manage dependencies between teams 11. The Nexus framework defines the accountabilities, events, and artifacts that bind and weave together the work of the teams in a Nexus 11. One of the key events in the Nexus framework is the Nexus Sprint Planning, which is used to coordinate the activities of all teams in the Nexus for a single Sprint 11.
In Scenario B, the Nexus is developing a complex product with different parts that only certain teams can work on. There are also some highly specialized individuals outside the Nexus that are required for some of the work. In past Sprints, the Nexus encountered challenges dealing with the many dependencies between teams. Dependencies are the relationships between the work items that affect the order, timing, or outcome of the work 22. Dependencies can cause delays, rework, waste, and lower quality 22. Therefore, it is important to identify and resolve dependencies as early and as often as possible 22.
The two strategies that would be most effective in dealing with the dependencies are:
Discover and document dependent work during Cross-Team Refinement of the Product Backlog, so teams are aware of dependencies before Nexus Sprint Planning. This will allow Nexus Sprint Planning to focus on resolving dependencies for the upcoming Sprint. This is answer A. This is a valid strategy because Cross-Team Refinement is an activity where representatives from each team in the Nexus meet to decompose and refine the Product Backlog items into smaller pieces of work that can be delivered by a single team or multiple teams 11. By doing this, the teams can discover and document the dependent work that needs to be done by other teams or external parties 11. This will help the teams to be aware of the dependencies before the Nexus Sprint Planning and to prepare for them 11. This will also allow the Nexus Sprint Planning to focus on resolving the dependencies for the upcoming Sprint, rather than spending time on identifying them 11.
During Nexus Sprint Planning, have appropriate representatives from each team in the Nexus briefly meet to discuss dependencies for the upcoming Sprint. This conversation will help their individual team's Sprint Planning. This is answer C. This is a valid strategy because Nexus Sprint Planning is an event where the Nexus, consisting of the Product Owner and appropriate representatives from each team, meet to plan the Sprint 11. The purpose of Nexus Sprint Planning is to coordinate the activities of all teams in the Nexus for a single Sprint 11. The result of Nexus Sprint Planning is a Nexus Sprint Goal that aligns with the Product Goal and a Nexus Sprint Backlog that contains the work to be done by the teams to achieve the Nexus Sprint Goal 11. During Nexus Sprint Planning, the representatives from each team can briefly meet to discuss the dependencies for the upcoming Sprint and how to resolve them 11. This conversation will help their individual team's Sprint Planning, where they can create their own team Sprint Goal and team Sprint Backlog that support the Nexus Sprint Goal and the Nexus Sprint Backlog 11.
The other two answers are not correct because:
Have the Nexus Integration Team order the Nexus Sprint Backlog. They should control and resolve the dependencies. This is answer B. This is not a valid strategy because the Nexus Integration Team is not the owner or the controller of the Nexus Sprint Backlog. The Nexus Integration Team is a role that consists of the Scrum Master, the Product Owner, and other members who are responsible for coordinating, coaching, and supervising the integration of the work done by the teams in the Nexus 1[1][5]. The Nexus Integration Team facilitates the Nexus Sprint Planning, but does not order or dictate the Nexus Sprint Backlog 1[1][5]. The Nexus Sprint Backlog is owned and managed by the Nexus, not by the Nexus Integration Team 1[1][5]. The Nexus Integration Team helps the teams to identify and resolve the dependencies, but does not control or impose them 1[1][5].
Gather all people in the Nexus into a 48-hour Nexus Sprint Planning event. Discover, document, and resolve dependencies during this time. This is answer D. This is not a valid strategy because gathering all people in the Nexus into a 48-hour Nexus Sprint Planning event is not feasible, efficient, or effective. The Nexus Sprint Planning is not meant to be a long and exhaustive event that involves all people in the Nexus 11. The Nexus Sprint Planning is meant to be a short and focused event that involves only the Product Owner and appropriate representatives from each team in the Nexus 11. The Nexus Sprint Planning is not meant to be the only time to discover, document, and resolve dependencies 11. The Nexus Sprint Planning is meant to be the time to coordinate the activities of the teams for the upcoming Sprint and to create a Nexus Sprint Goal and a Nexus Sprint Backlog 11. The discovery, documentation, and resolution of dependencies should be done continuously throughout the Sprint, not only during the Nexus Sprint Planning 11.
True or False: There is one Product Backlog for a Nexus.
Correct Answer:
A
Which statements are true when multiple Scrum Teams work on a product at the same time?
(choose the best two answers)
Correct Answer:
A, C
Explanation
The Nexus framework is a way of scaling Scrum for multiple teams working on a single product. The Nexus framework uses Scrum as its building block and extends it only where necessary to minimize and manage dependencies between teams 11. The Nexus framework defines the accountabilities, events, and artifacts that bind and weave together the work of the teams in a Nexus 11. One of the key artifacts in the Nexus framework is the Integrated Increment, which is the integrated aggregation of all work completed by all the Scrum Teams in a Nexus 112.
When multiple Scrum Teams work on a product at the same time, the statements that are true are:
The different Scrum Teams coordinate their work to deliver a single Increment. This is answer A. This is a valid answer because the different Scrum Teams in a Nexus are not working in isolation, but rather collaborating and coordinating their work to deliver a single Increment 113. The single Increment is the Integrated Increment, which is the sum of all the work done by the Scrum Teams in a Sprint that meets the Definition of Done 112. The single Increment is the potentially releasable outcome of the Sprint, which means it meets the quality standards and expectations of the stakeholders 112.
The Developers must integrate their work before the end of the Sprint. This is answer C. This is a valid answer because the Developers are the people who do the work of delivering a potentially releasable Increment of product value in each Sprint 114. The Developers must integrate their work before the end of the Sprint, which means they must combine and verify their work frequently and continuously throughout the Sprint 114. The integration of the work is essential for ensuring the quality and usability of the product, as well as for validating the assumptions and learning from the feedback 114.
The other three answers are not correct because:
Each Scrum Team develops one or more product components which the Nexus Integration team uses to assemble the Integrated Increment. This is answer B. This is not a valid answer because the Nexus Integration Team is not the one who assembles the Integrated Increment. The Nexus Integration Team is a role that consists of the Scrum Master, the Product Owner, and other members who are responsible for coordinating, coaching, and supervising the integration of the work done by the Scrum Teams in the Nexus 11[5]. The Nexus Integration Team facilitates the integration of the work, but does not do it for the teams 11[5]. The teams are responsible for integrating their own work and delivering a potentially releasable Increment of product value in each Sprint 11[5].
They are all on the same Scrum Team. This is answer D. This is not a valid answer because they are not all on the same Scrum Team. A Scrum Team is a small group of people who are cross-functional and self-organizing, and who deliver a potentially releasable Increment of product value in each Sprint 11[6]. A Scrum Team usually consists of one Scrum Master, one Product Owner, and a few Developers 11[6]. When multiple Scrum Teams work on a product at the same time, they are not on the same Scrum Team, but rather on different Scrum Teams that form a Nexus 11[6]. A Nexus is a group of three to nine Scrum Teams who work on a single product and who share a common Product Backlog, a common Definition of Done, and a common Sprint Goal 11[6].
The Scrum of Scrums assembles the components into an Integrated Increment. This is answer E. This is not a valid answer because the Scrum of Scrums is not a part of the Nexus framework. The Scrum of Scrums is a term that is sometimes used to describe a coordination mechanism for multiple Scrum Teams, where representatives from each team meet regularly to share information and align their work [7][7]. The Scrum of Scrums is not a formal event or role in Scrum or Nexus, and it is not the one who assembles the components into an Integrated Increment [7][7]. The teams are responsible for integrating their own work and delivering a potentially releasable Increment of product value in each Sprint 11[5].
How should Product Backlog items be chosen when multiple Scrum Teams work from the same
Product Backlog?
(choose the best answer)
Correct Answer:
B
Explanation
When multiple Scrum Teams work from the same Product Backlog, they should choose the Product Backlog items that they can deliver as part of an Integrated Increment, which is the combined work of all the Scrum Teams that meets the Nexus Sprint Goal 11. The Developers, who are the people in the Scrum Teams who are accountable for creating and delivering the Increment, should pull work in agreement with the Product Owner, who is the person who is accountable for maximizing the value of the product and the work performed and integrated by the Scrum Teams 11. The Developers and the Product Owner should collaborate to select the Product Backlog items that are most valuable, feasible, and aligned with the Nexus Sprint Goal 2233. Therefore, statement B is the correct answer.
Statement A is incorrect because it implies that the Scrum Teams choose the Weighted Shortest Job First, which is a prioritization technique that ranks Product Backlog items based on their value and cost 44. However, the Scrum Guide does not prescribe any specific technique for ordering the Product Backlog, and the Product Owner is the sole person responsible for managing the Product Backlog [5]. Statement C is incorrect because it suggests that each Scrum Team takes an equal number of items, which may not reflect the value, complexity, or dependencies of the items 1122. Statement D is incorrect because it assumes that the Scrum Team with the highest velocity pulls Product Backlog items first, which may not be the best way to optimize the value delivery and integration across the Nexus 1122. Statement E is incorrect because it proposes that the Product Owner should provide each team with its own Product Backlog, which would create confusion, inconsistency, and duplication of work. Having multiple Product Backlogs would also undermine the transparency and alignment that are essential for scaling Scrum 1122.
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.
The purpose of the Nexus Integration Team is to:
(choose the best two answers)
Correct Answer:
A, C
Explanation
The Nexus framework is a way of scaling Scrum for multiple teams working on a single product. The Nexus framework uses Scrum as its building block and extends it only where necessary to minimize and manage dependencies between teams 12. The Nexus framework defines the accountabilities, events, and artifacts that bind and weave together the work of the teams in a Nexus 12. One of the key roles in the Nexus framework is the Nexus Integration Team, which is a team of people who are responsible for coordinating, coaching, and supervising the integration of the work done by the Scrum Teams in the Nexus 21.
The purpose of the Nexus Integration Team is to:
Raise transparency. This is answer A. This is a valid answer because the Nexus Integration Team is responsible for raising transparency across the Nexus 213. Transparency is one of the pillars of empiricism, which is the principle of making decisions based on observation, inspection, and adaptation 12. The Nexus Integration Team helps to raise transparency by facilitating the Nexus events, such as the Nexus Sprint Planning, the Nexus Daily Scrum, the Nexus Sprint Review, and the Nexus Sprint Retrospective 213. The Nexus Integration Team also helps to raise transparency by visualizing the Nexus Sprint Backlog, which is a representation of the work across the Nexus that has dependencies 213. The Nexus Integration Team also helps to raise transparency by communicating and collaborating with the stakeholders, the Product Owner, and the Scrum Teams 213.
Be accountable that an Integrated Increment is produced. This is answer C. This is a valid answer because the Nexus Integration Team is accountable that an Integrated Increment is produced 214. The Integrated Increment is the integrated aggregation of all work completed by all the Scrum Teams in a Nexus 124. The Integrated Increment is the potentially releasable outcome of the Sprint, which means it meets the quality standards and expectations of the stakeholders 124. The Nexus Integration Team is accountable that an Integrated Increment is produced by ensuring that the work done by the Scrum Teams meets the Definition of Done, which is a formal description of the state of the Increment when it meets the quality measures required for the product 214. The Nexus Integration Team is also accountable that an Integrated Increment is produced by helping the Scrum Teams to identify and resolve any integration issues or dependencies that may affect the quality and delivery of the product 214.
The other two answers are not correct because:
Manage the Nexus. This is answer B. This is not a valid answer because the Nexus Integration Team is not the manager of the Nexus. The Nexus Integration Team is a role that consists of the Scrum Master, the Product Owner, and other members who are responsible for coordinating, coaching, and supervising the integration of the work done by the Scrum Teams in the Nexus 211. The Nexus Integration Team does not manage or control the Nexus, but rather supports and enables the Nexus 211. The Nexus is self-organizing and autonomous, which means it decides how to do its work and what work to do 124.
Integrate the work of the Scrum Teams. This is answer D. This is not a valid answer because the Nexus Integration Team is not the one who integrates the work of the Scrum Teams. The Nexus Integration Team is a role that consists of the Scrum Master, the Product Owner, and other members who are responsible for coordinating, coaching, and supervising the integration of the work done by the Scrum Teams in the Nexus 211. The Nexus Integration Team facilitates the integration of the work, but does not do it for the teams 211. The teams are responsible for integrating their own work and delivering a potentially releasable Increment of product value in each Sprint 124.
Full Access
Get the complete SPS question set
- 40 questions covering all exam domains
- Correct answers with explanations, like the free questions above
- PDF and online practice test
- 90 days of free updates
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.
Sample question from this domain above:
Q4
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:
Q1
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:
Q2Q3Q5Q6
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.
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.
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.
