SPS Dumps with Practice Exam Questions Answers

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.

Scrum Teams do not have to report back to the Nexus Integration Team right after their individual Daily Scrums. 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 14. The Nexus Daily Scrum is an event where the Nexus Integration Team and one or two representatives from each Scrum Team meet to inspect the current state of the Integrated Increment and identify any integration issues or dependencies 12. The Nexus Daily Scrum takes place before the individual Daily Scrums of the Scrum Teams 13. The purpose of the Nexus Daily Scrum is to coordinate any challenges and dependencies of the day that all teams should be aware of, not to report back to the Nexus Integration Team 12. The individual Daily Scrums of the Scrum Teams are focused on planning how to fix the integration problems and achieve the Sprint Goal 13. Therefore, the statement is false.

Using Scrum does not ensure that adding more resources to a product delivery effort proportionally increases the value delivered. In fact, adding more resources may have the opposite effect, as it can introduce more complexity, communication overhead, coordination challenges, and integration issues that can reduce the productivity and quality of the Scrum Teams 12. Scrum does not prescribe a specific team size or composition, but it does recommend that the Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint 3. Scrum also emphasizes the importance of delivering a potentially releasable increment of the product at least once per Sprint, which enables the Scrum Team and the stakeholders to inspect the value delivered and adapt accordingly 4. Therefore, using Scrum does not guarantee that adding more resources will increase the value delivered, but rather that delivering value frequently and incrementally will optimize the value delivery.

A Nexus Integration Team is not accountable for ensuring that an Integrated Increment is produced at least once a Sprint. The Nexus Integration Team is a specialized Scrum Team that provides services and guidance to the Scrum Teams in the Nexus to ensure that the Integrated Increment is produced every Sprint 11. However, the Nexus Integration Team is not accountable for the integration of the work of the individual Scrum Teams, as this is the responsibility of the Scrum Teams themselves 22. The Nexus Integration Team helps the Scrum Teams to coordinate, coach, and supervise the application of Nexus and the operation of Scrum, but it does not take over their work or accountability 33. Therefore, the statement is false.

When a Nexus, which is a group of approximately three to nine Scrum Teams working on the same product, faces many dependencies during Nexus Sprint Planning, it can use some techniques to manage them effectively. One technique is to reorganize team members between the teams to eliminate cross-team dependencies. This can be done by forming feature teams or component teams based on the nature of the work and the skills required. By doing so, the Nexus can reduce the need for coordination and integration across teams, and increase the autonomy and ownership of each team 1122. Therefore, statement B is correct.

Another technique is to reorder Product Backlog items to better accommodate dependencies. This can be done by applying dependency management techniques such as dependency mapping, dependency inversion, dependency breaking, and dependency prioritization. By doing so, the Nexus can identify, visualize, resolve, and minimize the dependencies that affect the delivery of the Integrated Increment, which is the combined work of all the Scrum Teams in the Nexus that meets the Nexus Sprint Goal 334455. Therefore, statement D is also correct.

Statement A is incorrect because it implies that the Nexus Integration Team, which is a group of people who are accountable for ensuring the integration and delivery of the Integrated Increment, should do the dependent work ahead of the Sprint for the teams. This would create a bottleneck and a single point of failure, as well as undermine the self-organization and collaboration of the Scrum Teams 1122. Statement C is incorrect because it suggests that the Nexus should extend the Sprint so that the teams can have more time to complete the dependent work. This would violate the Scrum principle of time-boxing, which ensures that the Nexus delivers value frequently and incrementally, and inspects and adapts its process regularly 1122.