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

You have been assigned as the Scrum Master of six new Scrum Teams that will build one product. What conditions should you strive for in this scenario?(choose the best two answers)

• There should be six Product Owners, one for each Scrum Team.
• There should be six Product Owners, one of whom is chief Product Owner.
• The product has one Product Backlog.
• There should be only one Product Owner who is accountable for the success of the product.
• Each Scrum Team should have a separate Product Backlog.

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.

The Scrum Teams in a Nexus find they have simply too much work each Sprint to do to deliver a valuable and useful Increment. What could they try to improve their ability to produce an Increment for the next Sprint?(choose the best answer)

• Reduce the amount of work that the teams pull into the Sprint.
• Ask the Nexus Integration Team to extend the Sprint to allow more time for integration.
• Reduce the number of Scrum Teams to reduce complexity.
• Add another Scrum Team to the Nexus to increase capacity.

Scenario C: Dependencies and Product Backlog itemsDuring 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 techniques could help this Nexus manage their dependencies effectively? (choose the best two answers)

• The Nexus Integration Team should complete the dependent work ahead of the Sprint for the teams.
• Reorganize team members between the teams to eliminate cross-team dependencies.
• Extend the Sprint so that the teams can have more time to complete the dependent work.
• Reorder Product Backlog items to better accommodate dependencies.

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.

Scenario B: Six Team Nexus with complex dependenciesA 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)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.Have the Nexus Integration Team order the Nexus Sprint Backlog. They should control and resolve the dependencies.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.Gather all people in the Nexus into a 48-hour Nexus Sprint Planning event. Discover, document, and resolve dependencies during this time.

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

Scenario B: Six Team Nexus with complex dependenciesA 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.Some individual Scrum Teams in this Nexus have said that they do not see how the work they are doing is contributing to the product's progress. What is the best remedy for this situation?(choose the best answer)

• During Nexus Sprint Planning, have all the teams plan the Sprint together in one room, so they can see what other teams are working on.
• During Nexus Sprint Planning, ensure that all Scrum Teams understand the Nexus Sprint Goal.
• Ask the Scrum Master to explain to the teams that the Product Owner can choose which features to work on, as she has the final say.
• During Nexus Sprint Planning, ask each Scrum Team to create a Sprint Goal that describes the purpose of the Sprint.

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.

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.

True or False: A Nexus Integration Team is responsible for actually doing the integration work during the Sprint.

• True
• False