Which statements are true regarding using Scrum for large-scale product delivery?
(choose the best two answers)
Splitting a team member's time between multiple Scrum Teams is often less
productive than focusing that team member on a single team's Sprint Backlog.
Scrum requires all team members work full time on a single team.
Changes to the core Scrum framework are needed to be successful with Scrum
at large-scale.
A well-structured and refined Product Backlog can minimize and often eliminate
dependencies between multiple Scrum Teams working together on a product
during a Sprint.
The Answer Is:
A, DExplanation:
The true statements regarding using Scrum for large-scale product delivery are:
A. Splitting a team member’s time between multiple Scrum Teams is often less productive than focusing that team member on a single team’s Sprint Backlog. This statement is true because splitting a team member’s time between multiple teams can cause context switching, communication overhead, coordination challenges, and reduced commitment and accountability. It can also reduce the team’s ability to self-organize and deliver a potentially releasable product increment at the end of each Sprint. Therefore, it is recommended that team members focus on one team’s Sprint Backlog and work as a cross-functional and cohesive unit 1122.
D. A well-structured and refined Product Backlog can minimize and often eliminate dependencies between multiple Scrum Teams working together on a product during a Sprint. This statement is true because a well-structured and refined Product Backlog can help the Product Owner and the Scrum Teams to identify and prioritize the most valuable and feasible work items, and to decompose them into smaller and independent pieces that can be delivered by one or more teams. This can reduce the complexity and risk of integration and dependency management, and increase the flow and quality of value delivery 3344.
The other statements are false for the following reasons:
B. Scrum requires all team members work full time on a single team. This statement is false because Scrum does not prescribe how team members allocate their time or effort. Scrum only defines the roles, events, artifacts, and rules that guide the empirical process of product development. However, as mentioned above, it is often more productive and effective for team members to focus on one team’s Sprint Backlog and avoid splitting their time between multiple teams [5].
C. Changes to the core Scrum framework are needed to be successful with Scrum at large-scale. This statement is false because Scrum is a lightweight and adaptable framework that can be applied to any complex product development context, regardless of the size or scale. Scrum does not need to be changed or modified to be successful at large-scale, but rather scaled up or down according to the needs and goals of the product organization. There are various frameworks and approaches that can help scale Scrum, such as Nexus, LeSS, SAFe, and Scrum@Scale, but they all adhere to the core principles and values of Scrum [6] [7].
Four teams in a Nexus typically integrate their work only once, late in the Sprint. The teams
report that it takes many hours or days to integrate their work, which delays the Sprint's end. To
address this issue, which of the following would help?
(choose the best answer)
Integrating more frequently.
Doing more acceptance testing.
Doing more exploratory testing.
Using Behavior-Driven Development.
Investing in more Requirements Traceability.
All of the above.
The Answer Is:
AExplanation:
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.
A Nexus Daily Scrum:
(choose the best two answers)
Provides a single meeting where all Scrum Teams can update the Sprint
Backlog.
Is the same as a Scrum-of-Scrums.
Provides input into each Scrum Team's individual Daily Scrums to help them
better plan their days work.
Is only for the Nexus Integration Team to plan their work for the next 24-hours.
Is an opportunity to make integration issues transparent.
The Answer Is:
C, EExplanation:
The best answers for this question are:
C. Provides input into each Scrum Team’s individual Daily Scrums to help them better plan their days work. This answer is correct because the Nexus Daily Scrum is an event that helps the Scrum Teams in a Nexus to coordinate their work and identify any integration issues or dependencies that may affect their progress toward the Nexus Sprint Goal. The appropriate representatives from each Scrum Team attend the Nexus Daily Scrum and share relevant information and feedback that can help their teams plan their work for the next 24 hours 112233.
E. Is an opportunity to make integration issues transparent. This answer is also correct because the Nexus Daily Scrum is an event that enables the Scrum Teams in a Nexus to inspect the current state of the Integrated Increment and to make any integration issues or newly discovered cross-team dependencies transparent. The Nexus Daily Scrum also provides a forum for the Scrum Teams to collaborate and resolve any integration challenges or impediments that may arise during the Sprint 112244.
The other answers are not correct for the following reasons:
A. Provides a single meeting where all Scrum Teams can update the Sprint Backlog. This answer is not accurate because the Nexus Daily Scrum is not a meeting where all Scrum Teams update the Sprint Backlog, but rather an event where appropriate representatives from each Scrum Team inspect the Integrated Increment and identify integration issues or dependencies. The Sprint Backlog is updated by each Scrum Team during their own Daily Scrum, which is a separate event from the Nexus Daily Scrum 1155.
B. Is the same as a Scrum-of-Scrums. This answer is not true because the Nexus Daily Scrum is not the same as a Scrum-of-Scrums, which is a common practice for coordinating multiple Scrum Teams that is not part of the Scrum framework. The Nexus Daily Scrum is a specific event defined by the Nexus framework, which is a minimal extension of Scrum that enables multiple Scrum Teams to work together on a single product. The Nexus Daily Scrum has a clear purpose, structure, and outcome that differs from a Scrum-of-Scrums 112233.
D. Is only for the Nexus Integration Team to plan their work for the next 24-hours. This answer is not correct because the Nexus Daily Scrum is not only for the Nexus Integration Team, but also for the appropriate representatives from each Scrum Team in the Nexus. The Nexus Integration Team is a special Scrum Team that facilitates the integration and delivery of the work done by the other Scrum Teams, but it does not plan the work for them. The Nexus Daily Scrum is an event that helps all the Scrum Teams in the Nexus to coordinate their work and identify any integration issues or dependencies 1155.
Who has overall responsibility for ensuring Nexus Sprint Retrospective occurs?
(choose the best answer)
The Scrum Master on the Nexus Integration Team.
Any Scrum Master from the Nexus.
The Nexus Integration Team.
The Developers.
The Answer Is:
CExplanation:
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.
Currently, your Scrum Teams are organized to address a single functional (component) area of
the product. What should be considered when deciding to move away from such component
teams toward feature teams?
(choose the best three answers)
Feature teams have less communication overhead.
With feature teams, it is easier to calculate the productivity per team.
You cannot do Scrum without feature teams.
When making this change, it helps to have support from the organization.
Productivity may decrease when making this kind of change.
The Answer Is:
A, D, EExplanation:
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.
During Cross-Team Refinement, the ordered Product Backlog (1 through 9) is mapped out so
the Nexus can visualize dependencies. For example, PBI 5 for Team Orange is dependent on
Team Red completing PBI 1.
All else being equal, which PBI is most concerning?
(choose the best answer)
PBI 2, because it has the most dependencies.
PBI 1, because it is on the top of the Product Backlog.
PBI 1, because it is the first piece of work with a dependency.
PBI 2, because there is a dependency with a different team on work that occurs
within the same Sprint.
The Answer Is:
DExplanation:
PBI 2 is the most concerning because it involves a cross-team dependency within the same Sprint, which can create challenges and risks for the integration and delivery of the product increment. According to the Online Nexus Guide1, dependencies should be minimized or eliminated as much as possible, and if they exist, they should be made transparent and resolved as early as possible. Cross-team dependencies within the same Sprint can cause delays, conflicts, rework, and waste, and reduce the quality and value of the product increment 234.
The other answers are not correct for the following reasons:
A. PBI 2, because it has the most dependencies. This answer is not accurate because PBI 2 does not have the most dependencies, but only one dependency with PBI 1 from Team Red. PBI 3 has the most dependencies, as it depends on PBI 1, PBI 2, and PBI 4. However, PBI 3 is not as concerning as PBI 2, because its dependencies are not within the same Sprint, but across different Sprints. This means that PBI 3 can be refined and planned in advance, and the teams can coordinate and communicate their work more effectively 5.
B. PBI 1, because it is on the top of the Product Backlog. This answer is not relevant because the position of PBI 1 on the Product Backlog does not indicate its level of concern, but its priority and value. The Product Backlog is ordered by the Product Owner based on various factors, such as business value, risk, complexity, and dependencies. PBI 1 may be on the top of the Product Backlog because it is the most valuable or urgent item, or because it is a prerequisite for other items, but it is not necessarily the most concerning item 6.
C. PBI 1, because it is the first piece of work with a dependency. This answer is not true because PBI 1 is not the first piece of work with a dependency, but the first piece of work that other items depend on. PBI 1 does not have any dependencies itself, but it creates dependencies for PBI 2, PBI 3, and PBI 5. Therefore, PBI 1 is not as concerning as PBI 2, because it does not depend on any other item, and it can be completed independently by Team Red 5.
If two Scrum Teams are added to a product that previously had only one Scrum Team, what will
be the immediate impact on the productivity of the original Scrum Team?
(choose the best answer)
Its productivity is likely to stay the same.
Its productivity is likely to decrease.
Its productivity is likely to increase.
The Answer Is:
BWhat is the purpose of Nexus Sprint Retrospective?
(choose the best answer)
Plan ways to increase quality and effectiveness across the whole Nexus.
To inspect how the last Sprint went with regards to individuals, teams, interactions,
processes, tools, and its Definition of Done.
To complement the Scrum Teams' Sprint Retrospectives by using bottom-up
intelligence to focus on issues that affect the Nexus as a whole.
All of the above.
The Answer Is:
DExplanation:
The purpose of Nexus Sprint Retrospective is all of the above, meaning that it aims to:
Plan ways to increase quality and effectiveness across the whole Nexus. The Nexus Sprint Retrospective is a formal opportunity for a Nexus to inspect and adapt itself and create a plan for improvements to be enacted during the next Sprint to ensure continuous improvement 11.
To inspect how the last Sprint went with regards to individuals, teams, interactions, processes, tools, and its Definition of Done. The Nexus Sprint Retrospective follows the same format and principles as the Scrum Team Sprint Retrospective, but at a larger scale. The Nexus inspects the aspects of the product development that affect the Nexus as a whole, such as the collaboration, the integration, the dependencies, the quality, and the value 22.
To complement the Scrum Teams’ Sprint Retrospectives by using bottom-up intelligence to focus on issues that affect the Nexus as a whole. The Nexus Sprint Retrospective does not replace the Scrum Teams’ Sprint Retrospectives, but rather enhances them by using the input and output from the individual teams to identify and address the shared challenges and opportunities 33.
True or False: A Nexus Integration Team is responsible for actually doing the integration work
during the Sprint.
True
False
The Answer Is:
BExplanation:
A Nexus Integration Team is not responsible for actually doing the integration work during the 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.
Scenario A: Nexus Sprint Review with Five Scrum Teams
There are five Scrum Teams working on a product. During the Nexus Sprint Review, the teams
present the results of the Sprint. After introductions, each team takes time to present their work
for inspection by individually showing the new features they have built. They are not using a
shared environment. The stakeholders do not provide much feedback. The event ends and
people filter out of the room.
What could help this Nexus create a single Integrated Increment for inspection at the Nexus
Sprint Review?
(choose the best answer)
Reserve the last few days of the Sprint for testing and integration.
Enforce a Definition of Done across the entire Nexus that includes integration.
Have the Nexus Integration Team integrate all the work as early as possible.
Have a Sprint dedicated to integration.
The Answer Is:
BExplanation:
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.