Free Scaled Professional Scrum (SPS) Exam SPS Exam Practice Test

True or False: Many Scrum Teams working on the same product create coordination challenges that can be fully addressed by creating a communication plan.

• True
• False

The purpose of the Nexus Sprint Backlog is:(choose the best two answers)

• To make the work of the Nexus Integration Team transparent.
• To provide a view of dependent Product Backlog items in a Sprint.
• To visualize all Product Backlog items.
• To make dependencies transparent to the Scrum Teams.

The purpose of the Nexus Integration Team is to: (choose the best two answers)Raise transparency.Manage the Nexus.Be accountable that an Integrated Increment is produced.Integrate the work of the Scrum Teams.

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

True or False: There is one Product Backlog for a Nexus.

• True
• False

If two Scrum Teams are added to a product that previously had only one Scrum Team, what will be the immediate impact on the productivity of the original Scrum Team?(choose the best answer)

• Its productivity is likely to stay the same.
• Its productivity is likely to decrease.
• Its productivity is likely to increase.

How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog?(choose the best answer)

• The Scrum Teams choose the Weighted Shortest Job First.
• The Developers pull work in agreement with the Product Owner.
• Each Scrum Team takes an equal number of items.
• The Scrum Team with the highest velocity pulls Product Backlog items first.
• The Product Owner should provide each team with its own Product Backlog.

True or False: A Nexus Integration Team is accountable for ensuring that a Integrated Increment is produced at least once a Sprint.

• True
• False

True or False: Using Scrum ensures that adding more resources to a product delivery effort proportionally increases the value delivered.

• True
• False

Four teams in a Nexus typically integrate their work only once, late in the Sprint. The teams report that it takes many hours or days to integrate their work, which delays the Sprint's end. To address this issue, which of the following would help?(choose the best answer)Integrating more frequently.Doing more acceptance testing.Doing more exploratory testing.Using Behavior-Driven Development.Investing in more Requirements Traceability.All of the above.

• Integrating more frequently. This answer is correct because integrating more frequently can help the Scrum Teams in a Nexus to detect and resolve integration issues or dependencies earlier and faster, and to deliver a potentially releasable product increment at the end of each Sprint. Integrating more frequently can also reduce the complexity and risk of integration, and increase the quality and feedback of value delivery 112233.
• The other answers are not correct for the following reasons:
• B . Doing more acceptance testing. This answer is not sufficient because doing more acceptance testing does not address the root cause of the problem, which is the late integration of the work. Acceptance testing can help to verify the quality and functionality of the product increment, but it does not ensure that the integration is done early and often. Moreover, doing more acceptance testing may consume more time and resources, and delay the delivery of the product increment 44. C . Doing more exploratory testing. This answer is not helpful because doing more exploratory testing does not solve the issue of the late integration of the work. Exploratory testing can help to discover and learn more about the product increment, but it does not guarantee that the integration is done smoothly and quickly. Furthermore, doing more exploratory testing may introduce more uncertainty and variability, and hinder the delivery of the product increment 55.
• D . Using Behavior-Driven Development. This answer is not relevant because using Behavior-Driven Development does not directly affect the integration of the work. Behavior-Driven Development is a technique that can help to define and communicate the expected behavior and outcomes of the product increment, but it does not ensure that the integration is done frequently and effectively.
• Additionally, using Behavior-Driven Development may require more collaboration and coordination, and complicate the delivery of the product increment [6].
• E . Investing in more Requirements Traceability. This answer is not useful because investing in more Requirements Traceability does not improve the integration of the work. Requirements Traceability is a practice that can help to track and document the origin and evolution of the product requirements, but it does not ensure that the integration is done timely and efficiently. Also, investing in more Requirements Traceability may increase the overhead and bureaucracy, and slow down the delivery of the product increment [7].
• F . All of the above. This answer is not correct because none of the above answers are effective for addressing the issue of the late integration of the work. As explained above, each of the above answers has its own limitations and drawbacks, and does not directly or sufficiently help the Scrum Teams in a Nexus to integrate their work more frequently and successfully. Therefore, the best answer is A. Integrating more frequently.

The purpose of a Nexus Sprint Retrospective is to:(choose the best two answers)

• Enable bottom-up intelligence to improve how the Scrum Teams in a Nexus are working together.
• Provide a forum for management to see how the Nexus is performing.
• Allow for inspection and adaptation of both individual Scrum Teams and a Nexus.
• Provide a single meeting to inspect and adapt how all Scrum Teams work together.