Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

PSM1 > Understanding and Apply Scrum [P8]: Scaling Scrum - The Nexus Guide > Flashcards

Understanding and Apply Scrum [P8]: Scaling Scrum - The Nexus Guide Flashcards

1
Q

What is nexus?

A
  • Framework
  • For developing and sustaining scaled product delivery initiatives
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What does Nexus built on?

A

Scrum

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

In general, where does Nexus build on Scrum?

A

Extends it only where absolutely necessary to minimize and manage dependencies between multiple Scrum Teams while promoting empiricism and the Scrum Values

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Where does Nexus inherit its purpose from and intent?

A

Scrum framework as per Scrum Guide

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Does Nexus change, level out or neglect any rules of Scrum?

A

Nope

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Who developed Nexus?

A

Ken Schwaber and Scrum.org

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Give the definition for a Nexu

A
  • group of 3-9 scrum teams
  • work together to deliver a single product
  • connected between people and things
  • 1 PO
  • 1 Product Backlog - all teams work from
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What does Nexus seek to preserve, enhance and enable?

A
  • preserve and enhance Scrum’s foundational bottom-up intelligence and empiricism
  • enable a group of Scrum Teams to deliver more value than can be achieved by a single team
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is the goal of Nexus?

A

scale the value that a group of Scrum Teams, working on a single product, is able to deliver

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

How does Nexus scale value?

A

reducing the complexity that those teams encoutner as they collaborate to deliver an integrated, valuable, useful product increment at least once every Sprint

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What common scaling problems does the Nexus Framework help teams solve?

A
  • reducing cross-team dependencies
  • preserve team self-management and transparency
  • ensuring accountability
  • makes transparent dependences
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are team dependencies often caused mismatches related to?

A
  • Product structure
  • Communication structure
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

In general, how does Nexus go about reducing or removing dependencies?

A

change the process, product structure and communication structure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What does “product structure” mean?

A

The degree to which different concerns are independently separated in the product will greatly affect the complexity of creating an integrated product release.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What does “communication structure” mean?

A

The way that people communicate within and between teams affects their ability to get work done; delays in communication and feedback reduce the flow of work.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

In general what key aspects of Scrum does Nexus extend?

A
  • Accountabilities
  • Events
  • Artifacts
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

How does Nexus extend Scrum accountabilities?

A
  • The Nexus Integration Team ensures that the Nexus delivers a valuable, useful Integrated Increment at least once every Sprint.
  • The Nexus Integration Team consists of the
    Product Owner, a Scrum Master, and Nexus Integration Team Members.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

How does Nexus extend Scrum events?

A
  • Events are appended to, placed around, or replace regular Scrum events to augment
    them.
  • As modified, they serve both the overall effort of all Scrum Teams in the Nexus, and each individual team.
  • A Nexus Sprint Goal is the objective for the Sprint.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

How does Nexus extend artifacts?

A
  • All Scrum Teams use the same, single Product Backlog.
  • As the Product Backlog items are refined and made ready, indicators of which team will most likely do the work inside a Sprint are made transparent.
  • A Nexus Sprint Backlog exists to assist with transparency during the Sprint.
  • The Integrated Increment represents the current sum of all integrated work completed by a Nexus.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What are the three specific sets of accountabilities with in a Scrum Team?

A
  • Developers (Devs + QA)
  • PO
  • SM
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What is the additional accountability that Nexus adds to the set of three existing Scrum accountabilities?

A

Nexus Integration Team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What is an Integrated Increment defined as?

A

the combined work completed by a Nexus

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

What is the Nexus Integration Team accountable for?

A
  • ensuring that a done integrated increment is produced at least once a sprint
  • providing a focus point of integration for the Nexus - allows for multiple scrum teams to come together to create valuable, useful increments, as prescribed by scrum, and be accountable for this
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

What common activities might a Nexus Integration Team perform?

A
  • coaching
  • consulting
  • highlighting awareness of dependencies and cross-team issues
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

Can the composition of the Nexus Integration Team change over time?

A

Yes - change to reflect the current needs of a Nexus

26
Q

Who makes up the Nexus Integration Team?

A
  • PO
  • SM
  • One or more Nexus Integration Team Members
27
Q

Explain the role of the PO in the Nexus Integration Team (i.e. the only PO in Nexus framework)

A
  • accountable for maximizing the value of the product and the work performed and
    integrated by the Scrum Teams in a Nexus
  • accountable for effective Product Backlog management. How this is done may vary widely across organizations, Nexuses,
    Scrum Teams, and individuals
27
Q

Explain the role of the SM in the Nexus Integration Team

A
  • accountable for ensuring the Nexus framework is understood and enacted as described in the Nexus Guide
  • may also be a Scrum Master in one or more of the Scrum Teams in the Nexus
27
Q

How many SMs in Nexus?

A
  • one for the Nexus Integration Team
  • one per Scrum Team in the Nexus
28
Q

Explain the role of the “one or more Nexus Integration Team Members” in the Nexus Integration Team

A

Scrum Team members who help the Scrum Teams to adopt tools and practices that contribute to the Scrum Teams’ ability to deliver a valuable and useful Integrated Increment that frequently meets the Definition of Done

29
Q

What is the Nexus Integration Team responsible for?

A
  • coaching and guiding the Scrum Teams to acquire, implement, and learn practices and tools that improve their ability to produce a valuable, useful Increment
30
Q

Which has precedence - membership in the Nexus Integration Team or the individual Scrum team membership? Why?

A
  • Nexus Integration Team
  • As long as their Nexus Integration Team responsibility is satisfied, they can work as team members of their respective Scrum Teams.
  • This preference helps ensure that the work to resolve issues affecting
    multiple teams has priority
31
Q

How do the length of Nexus events compare to the length of Scrum events?

A
  • Nexus events’ duration is guided by the length of the corresponding events in the Scrum guide
  • i.e. similar
  • they are timeboxes in addition to their corresponding Scrum events
32
Q

Is it practical for for all members of the Nexus to attend Nexus events?

A
  • At scale, not really
  • Hard for everyone to participate and agree
33
Q

Who attends Nexus events?

A

whichever members of the Nexus are needed to achieve the intended outcome of the event most effectively

34
Q

What events make up Nexus Events?

A
  • The Sprint
  • Cross-Team Refinement
  • Nexus Sprint Planning
  • Nexus Daily Scrum
  • Nexus Sprint Review
  • Nexus Sprint Retrospective
35
Q

Explain “The Sprint” Nexus Event

A
  • Same as in Scrum
  • Scrum Teams in a Nexus product a single Integrated Increment
36
Q

Explain the “Cross-Team Refinement” Nexus Event

A
  • Refine sole Product Backlog
  • reduces or eliminates cross-team dependenceis within a Nexus
  • PB is decomposed so dependencies are transparent, identified across teams, and removed/minimised
  • break down items from large and vague to actionable work that a single Scrum Team could deliver inside a sprint
  • ongoing
37
Q

What purposes does Cross-Team Refinement of the PB at scale serve?

A
  • helps the Scrum Teams forecast which team will deliver which Product Backlog items
  • identifies dependencies across those teams
38
Q

Comment on the frequency of Cross-Team Refinement in Nexus

A
  • ongoing
  • varies to optimize the two dual purposes of it
  • Where needed, each Scrum Team will continue their own refinement in order for the Product Backlog
    items to be ready for selection in a Nexus Sprint Planning event
39
Q

Explain the “Nexus Sprint Planning” Nexus Event

A
  • purpose - coordinate the activities of all Scrum Teams within a Nexus for a single Sprint
  • Appropriate representatives from each Scrum Team and the Product Owner meet to plan the Sprint
40
Q

What is the result of Nexus Sprint Planning?

A
  • a Nexus Sprint Goal that aligns with the Product Goal and describes the purpose that will be
    achieved by the Nexus during the Sprint
  • a Sprint Goal for each Scrum Team that aligns with the Nexus Sprint Goal
  • a single Nexus Sprint Backlog that represents the work of the Nexus toward the Nexus Sprint
    Goal and makes cross-team dependencies transparent
  • A Sprint Backlog for each Scrum Team, which makes transparent the work they will do in
    support of the Nexus Sprint Goal
41
Q

In Nexus, how many sprint backlogs are there?

A

one per Nexus Scrum Team

42
Q

Explain the “Nexus Daily Scrum” Nexus Event

A
  • purpose - identify any integration issues and inspect progress toward the Nexus Sprint Goal.
  • Appropriate representatives from the Scrum Teams attend the Nexus Daily Scrum.
  • they inspect the current state of the integrated Increment, and identify integration issues and newly discovered cross-team dependencies or impacts.
  • Each Scrum Team’s Daily Scrum complements the
    Nexus Daily Scrum by creating plans for the day, focused primarily on addressing the integration issues raised during the Nexus Daily Scrum.
43
Q

Can Scrum Teams in Nexus adjust their plans outside of the Nexus Daily Scrum?

A

Yes - Cross-team communication can occur throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint’s work

44
Q

Is there just one Daily Scrum in Nexus?

A

No - Nexus Integration Team and Scrum Team do one each

45
Q

Explain the “Nexus Sprint Review” Nexus Event

A
  • held at the end of the Sprint
  • to provide feedback on the done Integrated
    Increment that the Nexus has built over the Sprint and determine future adaptations
  • replaces individual Scrum Team Reviews - i.e. just one
  • Nexus presents the results of their work to key stakeholders and progress toward the Product Goal is discussed, although it may not be possible to show all completed work in detail
  • Based on this information, attendees collaborate on what the Nexus should do to address the feedback.
  • The Product Backlog may be adjusted to reflect these discussions.
46
Q

Do Scrum Teams do individual Sprint Reviews?

A

No - just one presented by the Nexus

47
Q

Explain the “Nexus Sprint Retrospective” Event

A
  • plan ways to increase quality and effectiveness across the whole Nexus
  • The Nexus inspects how the last Sprint went with regards to individuals, teams, interactions, processes, tools, and its Definition of Done
  • In addition to individual team improvements,
    the Scrum Teams’ Sprint Retrospectives complement the Nexus Sprint Retrospective by using bottom-up
    intelligence to focus on issues that affect the Nexus as a whole
  • Nexus Sprint Retrospective concludes the Sprint
48
Q

How many retros per sprint in Nexus?

A

Nexus Sprint Review + one per Scrum Team

49
Q

What Nexus Artifacts extend the Scrum Artifacts?

A
  • Product Backlog
  • Nexus Sprint Backlog
  • Integrated Increment
50
Q

What is the commitment of the Nexus Artifact “Product Backlog”

A

Product Goal - describes the future state of the product and serves as a long-term goal of the Nexus

51
Q

What is the commitment of the Nexus Artifact “Nexus Sprint Backlog”?

A

Nexus Sprint Goal

52
Q

What is the commitment of the Integrated Increment?

A
  • DoD
53
Q

Explain the “Product Backlog” Nexus Artifact

A
  • a single Product Backlog that contains a list of what is needed to improve the product for the entire Nexus and all of its Scrum Teams
  • At scale, the Product Backlog must be understood at a level where dependencies can be detected and minimized
  • Product Owner is accountable for the Product
    Backlog, including its content, availability, and ordering
54
Q

Explain the “Nexus Sprint Backlog” Nexus Artifact

A
  • composite of the Nexus Sprint Goal and Product Backlog items from the Sprint Backlogs of the individual Scrum Teams
  • used to highlight dependencies and the flow of work during the Sprint
  • Nexus Sprint Backlog is updated throughout the Sprint as more is learned
  • should have enough detail that the Nexus can inspect their progress in the Nexus Daily Scrum
55
Q

Explain the Nexus Sprint Goal

A
  • a single objective for the Nexus
  • sum of all the work and Sprint Goals of the Scrum Teams within the Nexus
  • creates coherence and focus for the Nexus for the Sprint by encouraging the Scrum Teams to work together rather than on separate initiatives
  • created at the Nexus Sprint Planning event and added to the Nexus Sprint Backlog
  • As Scrum Teams work during the Sprint, they keep the Nexus Sprint Goal in mind
  • The Nexus should demonstrate the valuable and useful functionality that is done to achieve the Nexus Sprint Goal at the Nexus Sprint Review in order to receive stakeholder feedback
56
Q

Explain the “Integrated Increment” Nexus Artifact

A
  • represents the current sum of all integrated work completed by a Nexus toward the Product Goal
  • inspected at the Nexus Sprint Review, but may be
    delivered to stakeholders before the end of the Sprint
  • must meet the Definition of Done
57
Q

Explain the DoD in the context of the Nexus Framework

A
  • defines the state of the integrated work when it meets the quality and measures required for the product
  • The Increment is done only when integrated, valuable, and usable
  • Individual Scrum Teams self-manage to achieve this state
  • They may choose to apply a more stringent Definition of Done within their own teams, but cannot apply less rigorous criteria than agreed for the Integrated Increment
58
Q

Who is responsible for creating and maintaining the DoD within Nexus?

A

The Nexus Integration Team

59
Q

Who must adhere to the Nexus DoD?

A

All Scrum Teams within the Nexus must define and adhere to this Definition of Done

PSM1 (86 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions