SPS Exam Dumps : Scaled Professional Scrum (SPS) Exam

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 C, the Nexus Sprint Planning is not conducted effectively. The representatives from each of the 9-member Scrum Teams identify many dependencies, which 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. 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.

What should the Scrum Teams do to effectively deal with their dependencies is:

• Increase the frequency of Cross-Team Refinement to reduce dependencies. This is answer A. This is a valid answer 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 reduce the dependencies by breaking down the work into more manageable and independent units 11. The teams can also identify and resolve the dependencies before the Nexus Sprint Planning, which will make the planning easier and more effective 11. By increasing the frequency of Cross-Team Refinement, the teams can ensure that the Product Backlog items are ready and clear for the Nexus Sprint Planning 11.

The other three answers are not correct because:

• Merge the two Scrum Teams together that have the most dependencies with each other. This is answer B. This is not a valid answer because merging the two Scrum Teams together that have the most dependencies with each other is not a good solution. It implies that the teams are not able to collaborate and coordinate effectively with each other, and that they need to be in the same team to work on the same product 11. It also increases the size and complexity of the merged team, which can reduce its agility and productivity 11. It also does not address the root cause of the dependencies, which may be related to the product or communication structure 22.
• Institute quarterly meetings for planning out all dependencies between teams. This is answer C. This is not a valid answer because instituting quarterly meetings for planning out all dependencies between teams is not consistent with Scrum or Nexus. Scrum and Nexus require that the teams plan and deliver a potentially releasable Increment of product value in each Sprint, which is usually a few weeks long 11. Instituting quarterly meetings for planning out all dependencies between teams means that the teams are not planning or delivering any value or receiving any feedback in the Sprints 11. It also means that the teams are not able to adapt to the changing needs and expectations of the customers and users, which are essential for empiricism and agility 11.
• All of the above. This is answer D. This is not a valid answer because none of the above answers are valid. Therefore, choosing all of them is not a valid answer either.

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.

The purpose of Nexus Sprint Planning is to:

• Coordinate the activities of all the Scrum Teams in a Nexus. This is answer A. This is a valid answer because the 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 Nexus Sprint Planning helps the teams to align their work with the Product Goal, identify and resolve dependencies, and create a common understanding of the Sprint 11.
• Create a plan for the Sprint. This is answer D. This is a valid answer because the Nexus Sprint Planning is an event where the Nexus creates a plan for the 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. The Nexus Sprint Backlog is a visualization of the work across the Nexus that has dependencies 11. The Nexus Sprint Goal and the Nexus Sprint Backlog guide the teams throughout the Sprint 11.

The other two answers are not correct because:

• Discover all the dependencies between Product Backlog items. This is answer B. This is not a valid answer because the Nexus Sprint Planning is not the only time to discover all the dependencies between Product Backlog items. 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 Nexus Sprint Planning is a 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 of dependencies should be done continuously throughout the Sprint, not only during the Nexus Sprint Planning 11. One of the activities that can help the teams to discover dependencies before the Nexus Sprint Planning is the Cross-Team Refinement, 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 1[1][6].
• Ensure all teams are committing to the right work. This is answer C. This is not a valid answer because the Nexus Sprint Planning is not a time to ensure all teams are committing to the right work. The Nexus Sprint Planning is a 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 Nexus Sprint Planning is not a time to impose or dictate the work to the teams, but rather to collaborate and align the work with the Product Goal 11. The teams are self-organizing and autonomous, which means they decide how to do their work and what work to do 1[1][7]. The teams do not commit to the work, but rather forecast the work based on their capacity and understanding 1[1][7].

The Nexus Sprint Retrospective is an event where the Nexus, consisting of multiple Scrum Teams, inspects and adapts its processes, tools, interactions, and dependencies to improve its quality and effectiveness 11. The Nexus Sprint Retrospective occurs after the Nexus Sprint Review and before the next Nexus Sprint Planning 11. The Nexus Sprint Retrospective has two parts: a first part where representatives from each Scrum Team identify shared challenges and opportunities, and a second part where each Scrum Team conducts its own Sprint Retrospective 23.

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. The Nexus Integration Team has the overall responsibility for ensuring the Nexus Sprint Retrospective occurs 11. The Nexus Integration Team facilitates the first part of the Nexus Sprint Retrospective, where the representatives from each Scrum Team share their insights and challenges 11. The Nexus Integration Team also participates in the second part of the Nexus Sprint Retrospective, where each Scrum Team reflects on its own performance and improvement actions 11. The Nexus Integration Team helps the Scrum Teams to identify and resolve any cross-team impediments or dependencies that may affect the quality and delivery of the Integrated Increment 11.

The other three answers are not correct because:

• The Scrum Master on the Nexus Integration Team. This is answer A. This is not a valid answer because the Scrum Master on the Nexus Integration Team is not the only one responsible for ensuring the Nexus Sprint Retrospective occurs. The Scrum Master on the Nexus Integration Team is a member of the Nexus Integration Team, but not the sole accountable person for the event. The Scrum Master on the Nexus Integration Team helps to facilitate the Nexus Sprint Retrospective, but does not own or control it 11.
• Any Scrum Master from the Nexus. This is answer B. This is not a valid answer because any Scrum Master from the Nexus does not have the authority or the responsibility to ensure the Nexus Sprint Retrospective occurs. Any Scrum Master from the Nexus is a member of a Scrum Team, but not a member of the Nexus Integration Team. Any Scrum Master from the Nexus helps to facilitate the Sprint Retrospective of their own Scrum Team, but does not have the visibility or the influence over the other Scrum Teams or the Nexus as a whole 11.
• The Developers. This is answer D. This is not a valid answer because the Developers do not have the responsibility for ensuring the Nexus Sprint Retrospective occurs. The Developers are the people who do the work of delivering a potentially releasable Increment of product value in each Sprint 11. The Developers participate in the Nexus Sprint Retrospective, but they do not organize or facilitate it. The Developers provide feedback and suggestions for improvement, but they do not have the accountability or the authority to ensure the Nexus Sprint Retrospective occurs 11.