Ace Your SPS Scaled Professional Scrum 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 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 11.

In Scenario A, the Nexus Sprint Review is not conducted effectively. The teams are not using a shared environment to demonstrate the Integrated Increment, but rather showing their individual work. This means that the stakeholders cannot see the whole product and how it works together. The teams are also delaying the integration of their work, which can lead to quality issues, technical debt, and increased complexity 11. The stakeholders do not provide much feedback, which means that the Nexus cannot adapt to the changing needs and expectations of the customers and users. The event ends without any clear outcomes or next steps.

What could help this Nexus create a single Integrated Increment for inspection at the Nexus Sprint Review is:

• Enforce a Definition of Done across the entire Nexus that includes integration. This is answer B. This is a valid answer because the Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product 11. The Definition of Done is used to assess when work is complete on the product Increment 11. The Definition of Done is defined by the Nexus and applies to all the work done by the Scrum Teams in the Nexus 11. The Definition of Done should include integration as one of the criteria, which means that the work done by the teams should be integrated frequently and continuously throughout the Sprint 11. By enforcing a Definition of Done that includes integration, the Nexus can ensure that the Integrated Increment is usable and potentially releasable, which means it meets the quality standards and expectations of the stakeholders 11.

The other three answers are not correct because:

• Reserve the last few days of the Sprint for testing and integration. This is answer A. This is not a valid answer because reserving the last few days of the Sprint for testing and integration is not a good practice. It implies that the teams are not testing and integrating their work throughout the Sprint, but rather doing it at the end of the Sprint. This can lead to quality issues, technical debt, and increased complexity 11. It also reduces the time available for inspection and adaptation, which are essential for empiricism and agility 11.
• Have the Nexus Integration Team integrate all the work as early as possible. This is answer C. This is not a valid answer because the Nexus Integration Team is not the only one responsible for integrating all the work. 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 11. The Nexus Integration Team facilitates the integration of the work, but does not do it for the teams 11. The teams are responsible for integrating their own work and delivering a potentially releasable Increment of product value in each Sprint 11.
• Have a Sprint dedicated to integration. This is answer D. This is not a valid answer because having a Sprint dedicated to integration is not consistent with Scrum or Nexus. Scrum and Nexus require that the teams deliver a potentially releasable Increment of product value in each Sprint 11. Having a Sprint dedicated to integration means that the teams are not delivering any value or receiving any feedback in that Sprint 11. It also means that the teams are accumulating technical debt and complexity that will make integration more difficult and risky 11.

The Nexus Sprint Review is an event where the Nexus, consisting of multiple Scrum Teams, presents the Integrated Increment to the stakeholders for inspection and feedback 1. The Integrated Increment is the sum of all the work done by the Scrum Teams in a Sprint that meets the Definition of Done 1. The purpose of the Nexus Sprint Review is to inspect the outcome of the Sprint, discuss the progress toward the Product Goal, discuss any changes in the environment, and collaborate on what to do next 2.

In Scenario A, the Nexus Sprint Review is not conducted effectively. The teams are not using a shared environment to demonstrate the Integrated Increment, but rather showing their individual work. This means that the stakeholders cannot see the whole product and how it works together. The teams are also delaying the integration of their work, which can lead to quality issues, technical debt, and increased complexity 1. The stakeholders do not provide much feedback, which means that the Nexus cannot adapt to the changing needs and expectations of the customers and users. The event ends without any clear outcomes or next steps.

If this pattern continues for multiple Sprints, the effects may be:

• Quality will degrade as the teams delay creating a single Integrated Increment. This is answer B. By not integrating their work frequently and continuously, the teams will face more challenges and risks in ensuring that the product is functional, reliable, and usable. The teams will also miss the opportunity to validate their assumptions and learn from the feedback on the Integrated Increment 1.
• Ability to adapt will suffer as the stakeholders continue to disengage and not give feedback. This is answer D. By not engaging the stakeholders in a meaningful dialogue and collaboration, the Nexus will lose the insight and direction that the feedback provides. The Nexus will also risk building the wrong product or features that do not meet the needs and expectations of the customers and users. The stakeholders will also lose trust and confidence in the Nexus and the product 2.

The other two answers are not correct because:

• There will be more and more work to inspect so teams will need their own individual Sprint Reviews. This is answer A. This is not a valid effect because the Nexus Sprint Review replaces the individual Scrum Team Sprint Reviews 1. The Nexus Sprint Review is not a time for each team to present their work, but rather for the Nexus to present the Integrated Increment. The teams should not need their own Sprint Reviews, but rather focus on integrating their work and delivering a valuable product 1.
• Empiricism will suffer as the teams cannot produce a shared velocity. This is answer C. This is not a valid effect because velocity is not a measure of empiricism. Empiricism is the principle of making decisions based on observation, inspection, and adaptation 1. Velocity is a measure of the amount of work done by a team or a Nexus in a Sprint. Velocity is not a mandatory artifact or metric in Scrum or Nexus, and it does not reflect the quality or value of the work done 1.

The purpose of Nexus Sprint Planning is to coordinate the activities of all Scrum Teams within a Nexus for a single Sprint 1. To do this effectively, the Nexus needs to have a clear understanding of the dependencies between the teams and the work items, and to communicate and collaborate with each other and any outside experts as needed. Therefore, the best practices for this Nexus are:

• A. Ensure all Scrum Teams and outside experts are available during the Nexus Sprint Planning event and have a way of quickly communicating with each other. They should try to be together in the same room or use technology that makes it seem as if they are in the same room. This practice enables the Nexus to have a shared understanding of the Product Backlog, the Product Goal, and the Nexus Sprint Goal, and to resolve any issues or questions that may arise during the planning. It also allows the Nexus to leverage the expertise of the outside specialists who are required for some of the work 2.
• D. Visualize the known dependencies in the Product Backlog for all to see. As Scrum Teams select work for the Sprint, they can easily check for any dependent work and communicate with other teams. This practice helps the Nexus to identify and manage the dependencies between the teams and the work items, and to optimize the flow of value delivery. It also supports transparency and alignment within the Nexus 3.

The other two practices are not effective for this Nexus because:

• B. Plan one Scrum Team’s Sprint at a time before moving on to the next team. This way you can account for time zone differences and can communicate dependencies across all teams. This practice is not optimal because it does not allow the Nexus to plan the Sprint as a whole, and to adjust the work allocation and sequence based on the dependencies and the Nexus Sprint Goal. It also creates delays and inefficiencies in the planning process, and reduces the collaboration and feedback opportunities among the teams 4.
• C. Have the Nexus Integration Team select the work for each of the individual Scrum Teams. This allows the Nexus Integration Team to control the dependencies. This practice is not consistent with the Nexus framework, which states that the Nexus Integration Team does not select the work for the Scrum Teams, but rather facilitates the integration and delivery of the work done by the Scrum Teams. It also undermines the self-organization and empowerment of the Scrum Teams, and reduces their ownership and accountability for the work 1.

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.