Scrum SPS Dumps

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 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 best answer for this question is A. 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 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 12. The Nexus framework defines the accountabilities, events, and artifacts that bind and weave together the work of the teams in a Nexus 12. One of the key roles in the Nexus framework is the Nexus Integration Team, which is a team of people who are responsible for coordinating, coaching, and supervising the integration of the work done by the Scrum Teams in the Nexus 21.

The purpose of the Nexus Integration Team is to:

• Raise transparency. This is answer A. 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.

The best way for multiple Scrum Teams to deliver a valuable and useful Increment in a Sprint is to complete work that integrates with all of the other work from other Scrum Teams on the initiative. This means that the Scrum Teams collaborate and coordinate their work to produce a single Integrated Increment that meets the Definition of Done and the Product Goal. The Integrated Increment is the combined work of all the Scrum Teams that is potentially releasable and provides value to the customers and stakeholders 11.

The other options are not correct for the following reasons:

• Each Scrum Team delivering done Increments of its own area of responsibility and integrating them into a whole product during stabilization prior to release is not a good idea, as it violates the Scrum principles and values. The Scrum Guide states that the Scrum Team delivers a product Increment that is usable and valuable at the end of every Sprint, not at the end of the release 22. Delaying the integration until the stabilization phase would compromise the transparency, the feedback, and the adaptability of the Scrum Teams.
• Each Scrum Team providing a unique done Increment that includes the team’s added functionality is not a good idea, as it does not ensure that the product Increment is integrated and consistent across the initiative. The Scrum Guide states that the product Increment is the sum of all the Product Backlog items completed during a Sprint and all previous Sprints 22. If each Scrum Team provides a unique Increment, they may not be aligned with the Product Goal and the Definition of Done, and they may create conflicts or dependencies with other Scrum Teams.
• Functionality not integrated with the work of other Scrum Teams being delivered as unintegrated Increments to demonstrate the value created by the Scrum Teams unable to completely integrate their Increments is not a good idea, as it does not ensure that the product Increment is done and valuable. The Scrum Guide states that the product Increment must be usable and meet the Definition of Done 22. If some functionality is not integrated with the work of other Scrum Teams, it may not be usable or valuable to the customers and stakeholders, and it may introduce technical debt or quality issues.

The best remedy for this situation is to ensure that all Scrum Teams understand the Nexus Sprint Goal. The Nexus Sprint Goal is a commitment that describes the purpose that will be achieved by the Nexus during the Sprint. It aligns with the Product Goal and provides coherence and focus for the work of the Scrum Teams. By understanding the Nexus Sprint Goal, the Scrum Teams can see how their work contributes to the product’s progress and value delivery 1234.

The other answers are not effective for this situation because:

• A. 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. This answer is not sufficient because it does not address the root cause of the problem, which is the lack of a clear and shared purpose for the Sprint. Having all the teams plan the Sprint together may help them coordinate their work and identify dependencies, but it does not necessarily help them understand how their work relates to the product’s progress and value.
• C. 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. This answer is not helpful because it does not foster collaboration and alignment among the Scrum Teams. It also undermines the self-organization and empowerment of the Scrum Teams, and reduces their ownership and accountability for the work. The Product Owner is responsible for managing and ordering the Product Backlog, but the Scrum Teams are responsible for selecting and delivering the work for the Sprint.
• D. During Nexus Sprint Planning, ask each Scrum Team to create a Sprint Goal that describes the purpose of the Sprint. This answer is not optimal because it does not ensure that the Scrum Teams have a common objective and direction for the Sprint. Each Scrum Team may have a different Sprint Goal that may or may not align with the Nexus Sprint Goal and the Product Goal. This may lead to confusion, inconsistency, and sub-optimization of the product delivery.

The most important concern for multiple Scrum Teams when they are working from the same Product Backlog is minimizing dependencies between teams. Dependencies are the relationships or constraints that exist between the work items or the teams that affect the delivery of the product 11. Dependencies can cause delays, rework, waste, and quality issues, and they can reduce the agility and value delivery of the Scrum Teams 2233. Therefore, minimizing dependencies between teams is a critical concern for scaling Scrum effectively 112233.

Statement A is incorrect because meeting original scope projections is not a primary concern for multiple Scrum Teams working from the same Product Backlog. Scrum does not prescribe a fixed scope for the product, but rather embraces change and adaptation based on feedback and learning 44. The Product Backlog is a dynamic and emergent artifact that reflects the current understanding of the product vision, goals, and requirements 44. The Product Owner is responsible for managing the Product Backlog and ordering the items in a way that maximizes the value of the product and the work of the Scrum Teams 44. Therefore, meeting original scope projections is not a relevant or realistic concern for scaling Scrum.

Statement C is incorrect because clear definition of requirements is not the most important concern for multiple Scrum Teams working from the same Product Backlog. While having clear and well-defined requirements is desirable and beneficial for the Scrum Teams, it is not always possible or necessary in a complex and uncertain environment 44. Scrum does not require detailed upfront specifications, but rather encourages empirical discovery and experimentation through frequent delivery and feedback 44. The Product Backlog items are refined and clarified by the Product Owner and the Developers as they collaborate and learn more about the product and the users 44. Therefore, clear definition of requirements is not the most critical concern for scaling Scrum.

Statement D is incorrect because making sure there is enough work for everyone on every team is not the most important concern for multiple Scrum Teams working from the same Product Backlog. Scrum does not focus on maximizing the utilization of the Scrum Team members, but rather on maximizing the value of the product and the work of the Scrum Teams 44. The Scrum Teams are self-organizing and cross-functional, which means they can decide how to do their work and have all the skills needed to create a potentially releasable Increment 44. The Scrum Teams pull work from the Product Backlog in agreement with the Product Owner, and they commit to delivering an Integrated Increment that meets the Nexus Sprint Goal 1144. Therefore, making sure there is enough work for everyone on every team is not the most essential concern for scaling Scrum.

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.