Free Scrum SPS Exam Actual Questions

The questions for SPS were last updated On Dec 19, 2024

Question No. 1

During Cross-Team Refinement, the ordered Product Backlog (1 through 9) is mapped out so

the Nexus can visualize dependencies. For example, PBI 5 for Team Orange is dependent on

Team Red completing PBI 1.

All else being equal, which PBI is most concerning?

(choose the best answer)

Show Answer Hide Answer
Correct Answer: D

PBI 2 is the most concerning because it involves a cross-team dependency within the same Sprint, which can create challenges and risks for the integration and delivery of the product increment. According to the Online Nexus Guide1, dependencies should be minimized or eliminated as much as possible, and if they exist, they should be made transparent and resolved as early as possible. Cross-team dependencies within the same Sprint can cause delays, conflicts, rework, and waste, and reduce the quality and value of the product increment 234.

The other answers are not correct for the following reasons:

A . PBI 2, because it has the most dependencies. This answer is not accurate because PBI 2 does not have the most dependencies, but only one dependency with PBI 1 from Team Red. PBI 3 has the most dependencies, as it depends on PBI 1, PBI 2, and PBI 4. However, PBI 3 is not as concerning as PBI 2, because its dependencies are not within the same Sprint, but across different Sprints. This means that PBI 3 can be refined and planned in advance, and the teams can coordinate and communicate their work more effectively 5.

B . PBI 1, because it is on the top of the Product Backlog. This answer is not relevant because the position of PBI 1 on the Product Backlog does not indicate its level of concern, but its priority and value. The Product Backlog is ordered by the Product Owner based on various factors, such as business value, risk, complexity, and dependencies. PBI 1 may be on the top of the Product Backlog because it is the most valuable or urgent item, or because it is a prerequisite for other items, but it is not necessarily the most concerning item 6.

C . PBI 1, because it is the first piece of work with a dependency. This answer is not true because PBI 1 is not the first piece of work with a dependency, but the first piece of work that other items depend on. PBI 1 does not have any dependencies itself, but it creates dependencies for PBI 2, PBI 3, and PBI 5. Therefore, PBI 1 is not as concerning as PBI 2, because it does not depend on any other item, and it can be completed independently by Team Red 5.


Question No. 3

How might the Nexus evolve its Definition of Done over time?

(choose the best answer)

Show Answer Hide Answer
Correct Answer: C

The Definition of Done is a set of quality standards that apply to the Integrated Increment, which is the combined work of all the Scrum Teams in the Nexus that meets the Nexus Sprint Goal 11. The Definition of Done creates transparency and alignment among the Scrum Teams and the stakeholders, and ensures that the Integrated Increment is potentially releasable 22. The Definition of Done can evolve over time as the Nexus learns from its experience and feedback, and as the product complexity and quality expectations change 33. The best place to discuss and update the Definition of Done is at the Nexus Sprint Retrospective, which is an event that occurs at the end of the Sprint where the Nexus inspects and adapts its processes, tools, and interactions 11. The Nexus Integration Team, which is a group of people who are accountable for ensuring the integration and delivery of the Integrated Increment, is responsible for the Definition of Done, but they can involve the other Scrum Team members and stakeholders in the discussion and decision 1144. Therefore, statement C is the correct answer.

Statement A is incorrect because it implies that the Nexus Integration Team can unilaterally change the Definition of Done without consulting the other Scrum Teams or stakeholders, which would undermine the transparency and collaboration that are essential for scaling Scrum 1144. Statement B is incorrect because it suggests that the Definition of Done is owned by the larger development organization, which may not be familiar with the specific needs and challenges of the Nexus, and that the changes are communicated by stakeholders, who may not have the technical expertise or authority to do so 1144. Statement D is incorrect because it assumes that the Scrum Masters have the sole power to decide on changes to the Definition of Done, which would exclude the input and agreement of the Nexus Integration Team, the other Scrum Team members, and the stakeholders 1144.


Question No. 4

A Nexus Daily Scrum:

(choose the best two answers)

Show Answer Hide Answer
Correct Answer: C, E

The best answers for this question are:

C . Provides input into each Scrum Team's individual Daily Scrums to help them better plan their days work. This answer is correct because the Nexus Daily Scrum is an event that helps the Scrum Teams in a Nexus to coordinate their work and identify any integration issues or dependencies that may affect their progress toward the Nexus Sprint Goal. The appropriate representatives from each Scrum Team attend the Nexus Daily Scrum and share relevant information and feedback that can help their teams plan their work for the next 24 hours 112233.

E . Is an opportunity to make integration issues transparent. This answer is also correct because the Nexus Daily Scrum is an event that enables the Scrum Teams in a Nexus to inspect the current state of the Integrated Increment and to make any integration issues or newly discovered cross-team dependencies transparent. The Nexus Daily Scrum also provides a forum for the Scrum Teams to collaborate and resolve any integration challenges or impediments that may arise during the Sprint 112244.

The other answers are not correct for the following reasons:

A . Provides a single meeting where all Scrum Teams can update the Sprint Backlog. This answer is not accurate because the Nexus Daily Scrum is not a meeting where all Scrum Teams update the Sprint Backlog, but rather an event where appropriate representatives from each Scrum Team inspect the Integrated Increment and identify integration issues or dependencies. The Sprint Backlog is updated by each Scrum Team during their own Daily Scrum, which is a separate event from the Nexus Daily Scrum 1155.

B . Is the same as a Scrum-of-Scrums. This answer is not true because the Nexus Daily Scrum is not the same as a Scrum-of-Scrums, which is a common practice for coordinating multiple Scrum Teams that is not part of the Scrum framework. The Nexus Daily Scrum is a specific event defined by the Nexus framework, which is a minimal extension of Scrum that enables multiple Scrum Teams to work together on a single product. The Nexus Daily Scrum has a clear purpose, structure, and outcome that differs from a Scrum-of-Scrums 112233.

D . Is only for the Nexus Integration Team to plan their work for the next 24-hours. This answer is not correct because the Nexus Daily Scrum is not only for the Nexus Integration Team, but also for the appropriate representatives from each Scrum Team in the Nexus. The Nexus Integration Team is a special Scrum Team that facilitates the integration and delivery of the work done by the other Scrum Teams, but it does not plan the work for them. The Nexus Daily Scrum is an event that helps all the Scrum Teams in the Nexus to coordinate their work and identify any integration issues or dependencies 1155.


Question No. 5

Which statements are true when multiple Scrum Teams work on a product at the same time?

(choose the best two answers)

Show Answer Hide Answer
Correct Answer: A, C

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].