Questions for the SPS were updated on : Nov 21 ,2025
The purpose of the Nexus Integration Team is to:
(choose the best two answers)
AC
Explanation:
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
. The Nexus framework defines the accountabilities,
events, and artifacts that bind and weave together the work of the teams in a Nexus
. 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
.
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
. 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
.
Which statements are true when multiple Scrum Teams work on a product at the same time?
(choose the best two answers)
AC
Explanation:
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
. The Nexus framework defines the accountabilities,
events, and artifacts that bind and weave together the work of the teams in a Nexus
. 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
[5]. The Nexus Integration Team facilitates the integration of the work,
but does not do it for the teams
[5]. The teams are responsible for integrating their own work and
delivering a potentially releasable Increment of product value in each Sprint
[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
[6]. A Scrum Team usually consists of one Scrum Master, one Product Owner, and a few
Developers
[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
[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
[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
[5].
The purpose of Nexus Sprint Planning is to:
(choose the best two answers)
AD
Explanation:
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
. The Nexus framework defines the accountabilities,
events, and artifacts that bind and weave together the work of the teams in a Nexus
. 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
.
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
. The purpose of Nexus Sprint
Planning is to coordinate the activities of all teams in the Nexus for a single Sprint
. 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
.
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
. 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
. The Nexus Sprint
Backlog is a visualization of the work across the Nexus that has dependencies
. The Nexus Sprint
Goal and the Nexus Sprint Backlog guide the teams throughout the Sprint
.
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
. Dependencies can cause delays, rework, waste,
and lower quality
. Therefore, it is important to identify and resolve dependencies as early and as
often as possible
. 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
. The discovery
of dependencies should be done continuously throughout the Sprint, not only during the Nexus
Sprint Planning
.
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
. 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
.
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].
Scenario C: Dependencies and Product Backlog items
During Nexus Sprint Planning, representatives from each of the 9-member Scrum Teams
identify many dependencies. This 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.
What should the Scrum Teams do to effectively deal with their dependencies?
(choose the best answer)
A
Explanation:
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
. The Nexus framework defines the accountabilities,
events, and artifacts that bind and weave together the work of the teams in a Nexus
. 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
.
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
. Dependencies can cause delays, rework, waste, and lower quality
.
Therefore, it is important to identify and resolve dependencies as early and as often as possible
.
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
. By doing this, the teams can reduce the
dependencies by breaking down the work into more manageable and independent units
. The
teams can also identify and resolve the dependencies before the Nexus Sprint Planning, which will
make the planning easier and more effective
. 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
.
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
. It also increases the size and complexity of the merged team, which
can reduce its agility and productivity
. It also does not address the root cause of the
dependencies, which may be related to the product or communication structure
.
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
. 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
. 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
.
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.
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)
B
Explanation:
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
. The Nexus framework defines the accountabilities,
events, and artifacts that bind and weave together the work of the teams in a Nexus
. 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
.
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
. 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
. The Definition of Done is used to
assess when work is complete on the product Increment
. The Definition of Done is defined by the
Nexus and applies to all the work done by the Scrum Teams in the Nexus
. 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
. 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
.
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
. It also reduces the time available for inspection and adaptation, which are
essential for empiricism and agility
.
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
. The Nexus Integration Team
facilitates the integration of the work, but does not do it for the teams
. The teams are responsible
for integrating their own work and delivering a potentially releasable Increment of product value in
each Sprint
.
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
. Having a
Sprint dedicated to integration means that the teams are not delivering any value or receiving any
feedback in that Sprint
. It also means that the teams are accumulating technical debt and
complexity that will make integration more difficult and risky
.
Scenario B: Six Team Nexus with complex dependencies
A six team Nexus is developing a complex product, with different parts of the product that only
certain Scrum Teams can work on. In fact, there are some highly specialized individuals outside
the Nexus that are required for some of the work. In past Sprints the Nexus encountered
challenges dealing with the many dependencies between Scrum Teams.
Which of the following two strategies would be most effective in dealing with their
dependencies?
(choose the best two answers)
AC
Explanation:
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
. The Nexus framework defines the accountabilities,
events, and artifacts that bind and weave together the work of the teams in a Nexus
. 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
.
In Scenario B, the Nexus is developing a complex product with different parts that only certain teams
can work on. There are also some highly specialized individuals outside the Nexus that are required
for some of the work. In past Sprints, the Nexus encountered challenges dealing with the many
dependencies between teams. Dependencies are the relationships between the work items that
affect the order, timing, or outcome of the work
. Dependencies can cause delays, rework, waste,
and lower quality
. Therefore, it is important to identify and resolve dependencies as early and as
often as possible
.
The two strategies that would be most effective in dealing with the dependencies are:
Discover and document dependent work during Cross-Team Refinement of the Product Backlog, so
teams are aware of dependencies before Nexus Sprint Planning. This will allow Nexus Sprint Planning
to focus on resolving dependencies for the upcoming Sprint. This is answer A. This is a valid strategy
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
. By doing this, the teams can discover and document
the dependent work that needs to be done by other teams or external parties
. This will help the
teams to be aware of the dependencies before the Nexus Sprint Planning and to prepare for them
. This will also allow the Nexus Sprint Planning to focus on resolving the dependencies for the
upcoming Sprint, rather than spending time on identifying them
.
During Nexus Sprint Planning, have appropriate representatives from each team in the Nexus briefly
meet to discuss dependencies for the upcoming Sprint. This conversation will help their individual
team’s Sprint Planning. This is answer C. This is a valid strategy because 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
. The purpose of Nexus Sprint Planning is to coordinate the activities
of all teams in the Nexus for a single Sprint
. 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
. During Nexus Sprint Planning, the representatives
from each team can briefly meet to discuss the dependencies for the upcoming Sprint and how to
resolve them
. This conversation will help their individual team’s Sprint Planning, where they can
create their own team Sprint Goal and team Sprint Backlog that support the Nexus Sprint Goal and
the Nexus Sprint Backlog
.
The other two answers are not correct because:
Have the Nexus Integration Team order the Nexus Sprint Backlog. They should control and resolve
the dependencies. This is answer B. This is not a valid strategy because the Nexus Integration Team is
not the owner or the controller of the Nexus Sprint Backlog.
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
[1][5].
The Nexus Integration Team facilitates the Nexus Sprint Planning, but does not order or
dictate the Nexus Sprint Backlog 1
[1][5].
The Nexus Sprint Backlog is owned and managed by the
Nexus, not by the Nexus Integration Team 1
[1][5].
The Nexus Integration Team helps the teams to
identify and resolve the dependencies, but does not control or impose them 1
[1][5].
Gather all people in the Nexus into a 48-hour Nexus Sprint Planning event. Discover, document, and
resolve dependencies during this time. This is answer D. This is not a valid strategy because gathering
all people in the Nexus into a 48-hour Nexus Sprint Planning event is not feasible, efficient, or
effective. The Nexus Sprint Planning is not meant to be a long and exhaustive event that involves all
people in the Nexus
. The Nexus Sprint Planning is meant to be a short and focused event that
involves only the Product Owner and appropriate representatives from each team in the Nexus
.
The Nexus Sprint Planning is not meant to be the only time to discover, document, and resolve
dependencies
. The Nexus Sprint Planning is meant to be the time to coordinate the activities of
the teams for the upcoming Sprint and to create a Nexus Sprint Goal and a Nexus Sprint Backlog
.
The discovery, documentation, and resolution of dependencies should be done continuously
throughout the Sprint, not only during the Nexus Sprint Planning
.
Who has overall responsibility for ensuring Nexus Sprint Retrospective occurs?
(choose the best answer)
C
Explanation:
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
. The Nexus Sprint Retrospective occurs after the Nexus Sprint Review and before the
next Nexus Sprint Planning
. 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
.
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
. The Nexus Integration Team has the overall
responsibility for ensuring the Nexus Sprint Retrospective occurs
. 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
. 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
. 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
.
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
.
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
.
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
. 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
.
True or False: Scrum Teams must report back to the Nexus Integration Team right after their
individual Daily Scrums.
B
Explanation:
Scrum Teams do not have to report back to the Nexus Integration Team right after their individual
Daily Scrums. The Nexus Integration Team is a role that consists of the Scrum Master, the Product
Owner, and other members who are responsible for coordinating, coaching, and supervising the
integration of the work done by the Scrum Teams in the Nexus
. The Nexus Daily Scrum is an event
where the Nexus Integration Team and one or two representatives from each Scrum Team meet to
inspect the current state of the Integrated Increment and identify any integration issues or
dependencies
. The Nexus Daily Scrum takes place before the individual Daily Scrums of the Scrum
Teams
. The purpose of the Nexus Daily Scrum is to coordinate any challenges and dependencies
of the day that all teams should be aware of, not to report back to the Nexus Integration Team
.
The individual Daily Scrums of the Scrum Teams are focused on planning how to fix the integration
problems and achieve the Sprint Goal
. 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.
If this pattern of Nexus Sprint Reviews continues for multiple Sprints, what may be the effects?
(choose the best two answers)
BD
Explanation:
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
.
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
.
From the list below, what is the most important concern for multiple Scrum Teams when they
are working from the same Product Backlog?
(choose the best answer)
B
Explanation:
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
.
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.
How should Product Backlog items be chosen when multiple Scrum Teams work from the same
Product Backlog?
(choose the best answer)
B
Explanation:
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
. 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
. 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
.
True or False: There is one Product Backlog for a Nexus.
A
Explanation:
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.
Scenario C: Dependencies and Product Backlog items
During Nexus Sprint Planning, representatives from each of the 9-member Scrum Teams
identify many dependencies. This 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.
What techniques could help this Nexus manage their dependencies effectively?
(choose the best two answers)
BD
Explanation:
When a Nexus, which is a group of approximately three to nine Scrum Teams working on the same
product, faces many dependencies during Nexus Sprint Planning, it can use some techniques to
manage them effectively. One technique is to reorganize team members between the teams to
eliminate cross-team dependencies. This can be done by forming feature teams or component teams
based on the nature of the work and the skills required. By doing so, the Nexus can reduce the need
for coordination and integration across teams, and increase the autonomy and ownership of each
team
1122
. Therefore, statement B is correct.
Another technique is to reorder Product Backlog items to better accommodate dependencies. This
can be done by applying dependency management techniques such as dependency mapping,
dependency inversion, dependency breaking, and dependency prioritization. By doing so, the Nexus
can identify, visualize, resolve, and minimize the dependencies that affect the delivery of the
Integrated Increment, which is the combined work of all the Scrum Teams in the Nexus that meets
the Nexus Sprint Goal
334455
. Therefore, statement D is also correct.
Statement A is incorrect because it implies that the Nexus Integration Team, which is a group of
people who are accountable for ensuring the integration and delivery of the Integrated Increment,
should do the dependent work ahead of the Sprint for the teams. This would create a bottleneck and
a single point of failure, as well as undermine the self-organization and collaboration of the Scrum
Teams
1122
. Statement C is incorrect because it suggests that the Nexus should extend the Sprint so
that the teams can have more time to complete the dependent work. This would violate the Scrum
principle of time-boxing, which ensures that the Nexus delivers value frequently and incrementally,
and inspects and adapts its process regularly
1122
.
The purpose of a Nexus Sprint Retrospective is to:
(choose the best two answers)
AC
Explanation:
The Nexus Sprint Retrospective is an event that occurs at the end of the Sprint where the Nexus,
which is a group of approximately three to nine Scrum Teams working on the same product, plans
ways to increase quality and effectiveness across the whole Nexus
. The purpose of the Nexus
Sprint Retrospective is to inspect and adapt the Nexus framework, the integrated work, the
processes, the tools, and the interactions among the Scrum Teams
. Therefore, statement C is
correct.
The Nexus Sprint Retrospective follows a three-step process: first, representatives from each Scrum
Team identify issues that affect multiple teams; second, each Scrum Team conducts its own Sprint
Retrospective; and third, representatives from each team meet again to discuss any actions needed
based on the shared challenges
112233
. The Nexus Sprint Retrospective enables bottom-up
intelligence to improve how the Scrum Teams in a Nexus are working together, as it allows the teams
to share their insights, learn from each other, and collaborate on solutions
44
. Therefore, statement
A is also correct.
Statement B is incorrect because the Nexus Sprint Retrospective is not a forum for management to
see how the Nexus is performing, but rather a time for the Nexus to self-organize and self-improve
1144
. Statement D is incorrect because the Nexus Sprint Retrospective is not a single meeting to
inspect and adapt how all Scrum Teams work together, but rather a combination of three meetings
that involve both individual and collective reflection and action
112233
.
You have been assigned as the Scrum Master of six new Scrum Teams that will build one
product. What conditions should you strive for in this scenario?
(choose the best two answers)
CD
Explanation:
When six new Scrum Teams are working on one product, they should form a Nexus, which is a
framework for scaling Scrum
. A Nexus has a single Product Owner who is accountable for
maximizing the value of the product and the work performed and integrated by the Scrum Teams
1122
. Therefore, statement D is correct.
A Nexus also works off a single Product Backlog, which is an ordered list of the work to be done by
the Scrum Teams in the Nexus
. The Product Backlog has a single source of requirements and
priorities for the product, and it is managed by the Product Owner
1122
. Therefore, statement C is
also correct.
Statements A, B, and E are incorrect because they imply that each Scrum Team has its own Product
Owner and Product Backlog, which would create confusion, inconsistency, and duplication of work.
Having multiple Product Owners and Product Backlogs would also undermine the transparency and
alignment that are essential for scaling Scrum
1122
.