A Nexus is a framework for scaling Scrum that enables multiple Scrum Teams to work on a single product 1. A Nexus has one Product Backlog, which is an ordered list of the work to be done by the Scrum Teams in the Nexus 1. The Product Backlog has a single source of requirements and priorities for the product, and it is managed by the Product Owner, who is accountable for maximizing the value of the product and the work performed and integrated by the Scrum Teams 1. Having one Product Backlog for a Nexus ensures that the Scrum Teams have a common vision, goal, and alignment for the product 23. Therefore, the statement is true.

When multiple Scrum Teams work from the same Product Backlog, they should choose the Product Backlog items that they can deliver as part of an Integrated Increment, which is the combined work of all the Scrum Teams that meets the Nexus Sprint Goal 11. The Developers, who are the people in the Scrum Teams who are accountable for creating and delivering the Increment, should pull work in agreement with the Product Owner, who is the person who is accountable for maximizing the value of the product and the work performed and integrated by the Scrum Teams 11. The Developers and the Product Owner should collaborate to select the Product Backlog items that are most valuable, feasible, and aligned with the Nexus Sprint Goal 2233. Therefore, statement B is the correct answer.

Statement A is incorrect because it implies that the Scrum Teams choose the Weighted Shortest Job First, which is a prioritization technique that ranks Product Backlog items based on their value and cost 44. However, the Scrum Guide does not prescribe any specific technique for ordering the Product Backlog, and the Product Owner is the sole person responsible for managing the Product Backlog [5]. Statement C is incorrect because it suggests that each Scrum Team takes an equal number of items, which may not reflect the value, complexity, or dependencies of the items 1122. Statement D is incorrect because it assumes that the Scrum Team with the highest velocity pulls Product Backlog items first, which may not be the best way to optimize the value delivery and integration across the Nexus 1122. Statement E is incorrect because it proposes that the Product Owner should provide each team with its own Product Backlog, which would create confusion, inconsistency, and duplication of work. Having multiple Product Backlogs would also undermine the transparency and alignment that are essential for scaling Scrum 1122.

According to the Nexus Guide1, the Nexus Sprint Review is an event where the Nexus presents the Done Integrated Increment that was built over the Sprint and collects feedback from the stakeholders. The Integrated Increment is the combined work of all the Scrum Teams in the Nexus that meets the Definition of Done. The Nexus Guide also states that 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.

In the scenario, the teams are not using a shared environment, which implies that they are not integrating their work frequently and effectively. This means that there is no single Integrated Increment that can be inspected and adapted by the stakeholders. This also suggests that the Nexus Integration Team is lacking or nonexistent, or that it is not fulfilling its role of facilitating integration and resolving dependencies. Without a Nexus Integration Team and a shared environment, the Nexus cannot deliver a valuable product Increment that meets the Product Goal.

The Sprint length and the integration phase are not relevant to the scenario. The Sprint length is determined by the Nexus based on the complexity and uncertainty of the product, and it should be less than a month. The integration phase is not a separate phase in Nexus, but a continuous activity that happens throughout the Sprint. Therefore, A and B are not correct answers.

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.

Creating a communication plan is not enough to fully address the coordination challenges that arise when many Scrum Teams work on the same product. A communication plan is a document that outlines the objectives, methods, channels, and frequency of communication among the stakeholders of a project or product 1. While a communication plan is useful for ensuring clarity, transparency, and alignment among the Scrum Teams and other parties involved, it does not address other aspects of coordination, such as integration, dependency management, alignment of goals and vision, and cross-team collaboration 2.

To effectively coordinate multiple Scrum Teams working on the same product, a communication plan should be complemented by other practices and frameworks, such as:

• Nexus: Nexus is a framework for scaling Scrum that consists of three to nine Scrum Teams working together to deliver an Integrated Increment every Sprint 3. Nexus provides roles, events, artifacts, and rules that help the Scrum Teams coordinate, integrate, and align their work, while maintaining the Scrum values and principles 4.
• Scrum of Scrums: Scrum of Scrums is a technique for scaling Scrum that involves a regular meeting of representatives from each Scrum Team to share progress, identify dependencies, resolve issues, and align on the product vision and goal . Scrum of Scrums helps the Scrum Teams communicate and collaborate effectively, while minimizing the overhead and complexity of coordination .
• Communities of Practice: Communities of Practice are groups of people who share a common interest, skill, or domain, and who meet regularly to exchange knowledge, ideas, and best practices . Communities of Practice help the Scrum Teams learn from each other, improve their skills, and foster a culture of continuous improvement .

Moving away from component teams toward feature teams is a significant change that should be considered carefully. Here are some of the factors that should be taken into account:

• Feature teams have less communication overhead than component teams, as they are able to deliver end-to-end customer features without relying on other teams or components 11. This reduces the complexity and the dependencies among the teams, and improves the transparency and the feedback loop. Feature teams also foster more collaboration and cross-functional learning among the team members, as they have to work on different aspects of the product 22.
• When making this change, it helps to have support from the organization, as it may require a shift in the culture, the structure, and the processes of the company 33. The organization should provide the necessary resources, training, and coaching to the teams to help them adopt the feature team model. The organization should also align its goals, incentives, and metrics with the feature team approach, and remove any barriers or impediments that may hinder the teams’ performance 44.
• Productivity may decrease when making this kind of change, as the teams may face some challenges and difficulties in the transition period 55. For example, the teams may have to learn new skills, technologies, or domains that they are not familiar with. The teams may also have to deal with legacy code, technical debt, or integration issues that may slow down their delivery. The teams may also experience some resistance or conflict from the existing component teams or stakeholders. Therefore, the teams should expect some temporary setbacks and losses in productivity, and focus on continuous improvement and adaptation.

The other options are not correct for the following reasons:

• With feature teams, it is not easier to calculate the productivity per team, as productivity is not a simple or straightforward metric to measure in software development [6]. Productivity depends on various factors, such as the quality, the value, the complexity, and the customer satisfaction of the product. Moreover, focusing on the productivity per team may create a competitive or individualistic mindset among the teams, rather than a collaborative or collective one. The teams should focus on delivering the best possible product Increment that meets the Product Goal and the Definition of Done, rather than on maximizing their productivity [7].
• You can do Scrum without feature teams, as Scrum does not prescribe any specific team structure or organization [8]. Scrum only requires that the Scrum Team is cross-functional, self-organizing, and accountable for delivering a potentially releasable product Increment every Sprint [9]. However, feature teams are generally more aligned with the Scrum values and principles, as they enable the teams to deliver customer-centric features faster and more frequently, and to respond to changes more effectively [10]. Therefore, feature teams are recommended, but not mandatory, for 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 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 purpose of the Nexus Sprint Backlog is to provide a view of dependent Product Backlog items in a Sprint and to make dependencies transparent to the Scrum Teams 15. The Nexus Sprint Backlog is a composite of the Product Backlog items from the Sprint Backlogs of the individual Scrum Teams, and it is used to highlight dependencies and the flow of work during the Sprint. It is updated throughout the Sprint as more is learned 21324354.

The other answers are not correct for the following reasons:

• A. To make the work of the Nexus Integration Team transparent. This answer is not accurate because the Nexus Sprint Backlog does not only show the work of the Nexus Integration Team, but also the work of all the Scrum Teams in the Nexus. The Nexus Integration Team is responsible for facilitating the integration and delivery of the work done by the Scrum Teams, but it does not select or assign the work for them 15.
• C. To visualize all Product Backlog items. This answer is not true because the Nexus Sprint Backlog does not contain all the Product Backlog items, but only the ones that the developers in the Nexus believe are necessary to achieve the Nexus Sprint Goal. The Product Backlog is the single source of requirements for the product, and it is managed and ordered by the Product Owner 15.

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

When multiple Scrum Teams work on a product at the same time, the statements that are true are:

• The different Scrum Teams coordinate their work to deliver a single Increment. This is answer A. This is a valid answer because the different Scrum Teams in a Nexus are not working in isolation, but rather collaborating and coordinating their work to deliver a single Increment 113. The single Increment is the Integrated Increment, which is the sum of all the work done by the Scrum Teams in a Sprint that meets the Definition of Done 112. The single Increment is the potentially releasable outcome of the Sprint, which means it meets the quality standards and expectations of the stakeholders 112.
• The Developers must integrate their work before the end of the Sprint. This is answer C. This is a valid answer because the Developers are the people who do the work of delivering a potentially releasable Increment of product value in each Sprint 114. The Developers must integrate their work before the end of the Sprint, which means they must combine and verify their work frequently and continuously throughout the Sprint 114. The integration of the work is essential for ensuring the quality and usability of the product, as well as for validating the assumptions and learning from the feedback 114.

The other three answers are not correct because:

• Each Scrum Team develops one or more product components which the Nexus Integration team uses to assemble the Integrated Increment. This is answer B. This is not a valid answer because the Nexus Integration Team is not the one who assembles the Integrated Increment. 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[5]. The Nexus Integration Team facilitates the integration of the work, but does not do it for the teams 11[5]. The teams are responsible for integrating their own work and delivering a potentially releasable Increment of product value in each Sprint 11[5].
• They are all on the same Scrum Team. This is answer D. This is not a valid answer because they are not all on the same Scrum Team. A Scrum Team is a small group of people who are cross-functional and self-organizing, and who deliver a potentially releasable Increment of product value in each Sprint 11[6]. A Scrum Team usually consists of one Scrum Master, one Product Owner, and a few Developers 11[6]. When multiple Scrum Teams work on a product at the same time, they are not on the same Scrum Team, but rather on different Scrum Teams that form a Nexus 11[6]. A Nexus is a group of three to nine Scrum Teams who work on a single product and who share a common Product Backlog, a common Definition of Done, and a common Sprint Goal 11[6].
• The Scrum of Scrums assembles the components into an Integrated Increment. This is answer E. This is not a valid answer because the Scrum of Scrums is not a part of the Nexus framework. The Scrum of Scrums is a term that is sometimes used to describe a coordination mechanism for multiple Scrum Teams, where representatives from each team meet regularly to share information and align their work [7][7]. The Scrum of Scrums is not a formal event or role in Scrum or Nexus, and it is not the one who assembles the components into an Integrated Increment [7][7]. The teams are responsible for integrating their own work and delivering a potentially releasable Increment of product value in each Sprint 11[5].