Brainscape's Knowledge GenomeTM

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


See full index

Scrum Nexus > SCRUM - Nexus > Flashcards

SCRUM - Nexus Flashcards

To help prepare to become Scaled Professional Scrum Certified with Scrum.org

1
Q

How can dependencies between Scrum Teams be reduced?

A

If

  • Requirements
  • Team Member Knowledge
  • Code / Test artifactsare mapped to the same team.

The Nexus Guide (Page 2)

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

What is the next step for work that is identified during the Nexus Daily SCRUM?

A

It is taken back to the individual SCRUM Teams for planning inside their Daily SCRUM events.

The Nexus Guide (Page 7)

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

Why does software development present additional difficulties?

A

Because its not physically present

The Nexus Guide (Page 2)

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

What is the best description of Nexus Sprint Planning?

A

Appropriate representatives from each SCRUM Team meet to discuss and review the refined Product Backlog.

The Nexus Guide (Page 4)

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

What is the first topic the cross-team Refinement should address?

A

Decomposing Product Backlog Items into enough detail in order to understand which teams might deliver them, and in what sequence over upcoming Sprints.

The Nexus Guide (Page 8)

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

What is the major difference between SCRUM Guidelines and Nexus Guidelines with respect to teams working together?

A

More attention is paid to dependencies and interoperation between SCRUM Teams, delivering one “Done” Integrated Increment at lease every Sprint.

The Nexus Guide (Page 3)

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

Who in the Nexus Plans out the Nexus Sprint Plan?

A

Each SCRUM Team plans its own Sprint, interacting with other teams as appropriate.

The Nexus Guide (Page 4)

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

When considering the number, frequency, duration and attendance of Refinement meetings what is the main driving factor?

A

Dependencies inherent in the Product Backlog

The Nexus Guide (Page 8)

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

In the Diagram what does 2 Represent?

A

Nexus Sprint PlanningThe Nexus Guide - Cover

The Nexus Guide (Page 10)

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

Who makes up the Nexus Integration Team?

A
  • Product Owner
  • SCRUM Master
  • Nexus Integration Team Members

The Nexus Guide (Page 3)

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

What is the “Nexus Sprint Backlog”?

A

An artifact that exists to assist with transparency during the Sprint, and collects the items which are refined and made ready, to indicate which team will perform the work during the Sprint.

The Nexus Guide (Page 3)

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

If all members of the SCRUM Teams, may do all of the work in the Nexus - then how do the SCRUM Teams select the most appropriate members to do the specific work?

A

Base on Dependencies

The Nexus Guide (Page 4)

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

Do SCRUM Teams within the Nexus maintain a joint Sprint Backlog?

A

No - All SCRUM Teams maintain their individual Sprint Backlog.

The Nexus Guide (Page 3)

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

Where should all product backlog items selected for the Sprint and their dependencies be visualized?

A

On the Nexus Sprint Backlog

The Nexus Guide (Page 7)

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

How do you know if enough refinement meetings have been performed during a Sprint?

A

If the Product Backlog items are ready and selectable with minimum dependencies during the Sprint Planning meeting.

The Nexus Guide (Page 9)

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

What part of the Nexus Sprint Retrospective allows the individual Sprint Teams to form actions to address issues during their individual SCRUM Team Sprint Retrospectives?

A

Each SCRUM Team holding their own Sprint Retro as described in the SCRUM Framework.

The Nexus Guide (Page 8)

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

What are the 3 parts to a Nexus Sprint Retrospective?

A

1 - Opportunity for appropriate representatives for across a Nexus to meeting and identify issues that have impacted more than a single team.
2 - Each SCRUM Team holding their own Sprint Retrospective as described in the SCRUM Framework.
3 - Opportunity for appropriate representative from the SCRUM Teams to meet again and agree on how to visualize and track identified actions.

The Nexus Guide (Page 7 - 8)

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

What is the second topic the cross-team Refinement should address? Why?

A

Identify Dependencies to provide visualization across teams and Sprints.This helps the team re-order the sequencing and allocation of their work in order to minimize the number of cross-team dependencies.

The Nexus Guide (Page 8 - 9)

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

In the Diagram what does 5 Represent?

A

Integrated IncrementThe Nexus Guide - Cover

The Nexus Guide (Page 10)

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

Who does the Nexus work during the Sprint?

A

“All work may be done by all members of the SCRUM Teams, as cross-functional members of the Nexus.”

The Nexus Guide (Page 4)

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

What roles are related to the “Nexus Integration Team”?

A
  • Nexus Product Owner
  • Nexus SCRUM Master
  • Nexus Integration Team Members

The Nexus Guide (Page 3)

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

What is the difference between the Nexus and SCRUM Team Product Owner?

A

None they are the same person - there can only be one Product Backlog - and one owner.

The Nexus Guide (Page 5)

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

Are Nexus ceremonies (Events) time-boxed?

A

Yes

The Nexus Guide (Page 6)

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

What is the role of the Product Owner in Sprint Planning?

A

Providing domain knowledge and guides selection and priority decisions.

The Nexus Guide (Page 6)

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

What is the focus of the Nexus Daily SCRUM?

A

Identify if any integration issues exist.

The Nexus Guide (Page 4)

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

What is the focus of the Nexus Daily SCRUM?

A
  • Inspect the current state of the integrated increment
  • ID Integration Issues
  • Review/ID newly discovered cross-team dependencies

The Nexus Guide (Page 7)

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

What allows the teams to monitor and minimize dependencies?

A

Visualization

The Nexus Guide (Page 8)

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

What best describes the “Nexus Framework”?

A

An exoskeleton that rests on top of multiple SCRUM Teams when they are combined to created an Integrated Increment.

The Nexus Guide (Page 3)

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

Should the SCRUM Team Sprint Planning and Nexus Sprint Planning be co-located?

A

Yes - the teams can continue to share newly found dependencies.

The Nexus Guide (Page 6)

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

What can be described as an exoskeleton that rests on top of multiple SCRUM Teams when they are combined to create an Integrated increment?

A

The Nexus Framework

The Nexus Guide (Page 3)

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

When should the Product Backlog be refined with dependencies identified and removed or minimized?

A

Prior to Nexus Sprint Planning.

The Nexus Guide (Page 7)

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

What makes the SCRUM Team select Product Backlog items and any dependencies transparent?

A

The Nexus Sprint Backlog

The Nexus Guide (Page 4)

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

Name the 4 Nexus Artifacts.

A
  • Product Backlog
  • Nexus Goal
  • Nexus Sprint Backlog
  • Integrated Increment

The Nexus Guide (Page 9)

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

What three questions should be asked at each Nexus Daily SCRUM?

A
  • Was the previous day’s work successfully integrated? (If not, why not)
  • What new dependencies have been identified
  • What information needs to be shared across teams in the Nexus

The Nexus Guide (Page 7)

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

What is the Nexus “Integrated Increment”?

A

The sum of all integrated work completed by the Nexus. The Integrated Increment must be useable and potentially releasable which means it much meet the definition of “Done”.

The Nexus Guide (Page 9)

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

What is the key factor is Nexus artifacts being effective?

A

Artifact Transparency.

The Nexus Guide (Page 10)

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

What common scaling dysfunctions every Retrospective should address?

A
  • Was any work left undone? Did the Nexus Generate Technical debt?
  • Were all artifacts, particularly code, frequently (as often as every day) successfully integrated.
  • Was the software successfully built, tested and deployed often enough to prevent the overwhelming accumulation of unresolved dependencies?

The Nexus Guide (Page 8)

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

Nexus Artifacts What is described as - Existing to assist with transparency during the Sprint, yet allowing SCRUM Teams to maintain their individual Sprint Backlogs?

A

The Nexus Sprint Backlogs -

The Nexus Guide (Page 3)

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

What does the Nexus Integration Team members do next if their primary responsibility is satisfied?

A

They may also work as Development (SCRUM) Team members in one or more SCRUM Teams.

The Nexus Guide (Page 6)

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

Which takes precedence the Nexus or SCRUM Team responsibilities? Why?

A

NexusIt helps ensure that the work to resolve issues that may affect teams (including other SCRUM Teams) has priority.

The Nexus Guide (Page 5)

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

What are the goals of the “Nexus Integration Team” with respect to deriving the best outcomes?

A
  • Coordinate
  • Coach
  • Supervise

The Nexus Guide (Page 3)

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

Why is having complete or near complete information vital?

A

Incomplete or partial information will lead to incorrect or flawed decisions. The impact in a Nexus is greatly magnified as the Nexus is composed of individual SCRUM Teams.

The Nexus Guide (Page 10)

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

How can dependencies be reduced between SCRUM Teams using Nexus?

A

To the extent that

  • requirements
  • team members’ knowledge
  • code/test artifactsare mapped to the same SCRUM Teams.

The Nexus Guide (Page 2)

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

What key ceremony does the following best describe”Appropriate representatives from each SCRUM Team meet to identify shared challenges.”

A

The Nexus Sprint Retrospective

The Nexus Guide (Page 4)

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

What Nexus artifact contains all the work and is constantly refined by the Nexus & SCRUM Teams?

A

The Product Backlog

The Nexus Guide (Page 9)

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

Who is responsible for the definition of “Done” in Nexus?

A

The Nexus Integration Team, with input from the Product Owner guided by the SCRUM Master.

The Nexus Guide (Page 6)

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

What is the purpose of the Nexus Framework?

A

Its a framework for

  • developing and sustaining scaled product
  • software development initiativesusing SCRUM as a building block.

The Nexus Guide (Page 2)

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

What should each SCRUM Team do next after the Nexus Sprint Retrospective?

A

Hold the SCRUM Team Retrospective. Appropriate representatives from each team meet again to discuss any actions needed based on shared challenges to provide bottom-up intelligence.

The Nexus Guide (Page 4)

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

What is the test for unacceptable technical debt?

A

When integration occurs, and it remains unclear that all dependencies are resolved. Unresolved dependencies remain hidden in the code and test base, lowering the overall value of the software.

The Nexus Guide (Page 10)

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

What is the purpose for during a Nexus Sprint Retrospective meeting and identifying issues that have impacted more than a single team?

A

Make shared issues transparent to all SCRUM Teams.

The Nexus Guide (Page 7)

51
Q

What 2 thoughts should be taken into account when ordering the Product Backlog?

A
  • Scope of Requirements may over lap
  • Manner in which they are implemented (may also affect the requirements).

The Nexus Guide (Page 2)

52
Q

In the Diagram what does 3 Represent?

A

Nexus Sprint BacklogThe Nexus Guide - Cover

The Nexus Guide (Page 10)

53
Q

What is the expected outcome of Nexus Sprint Planning?

A

A set of Sprint Goals that align with the overarching Nexus Goal, each SCRUM Team’s Sprint Backlog and a single Nexus Sprint Backlog.

The Nexus Guide (Page 4)

54
Q

What is the role of the SCRUM Master in the Nexus Team?

A

Overall responsibility for ensuring the Nexus framework is understood & enacted.

The Nexus Guide (Page 6)

55
Q

What is the role of the SCRUM Teams in Nexus Planning?

A

Appropriate reps validate and make adjustments to the ordering of the work as created during Nexus Refinement (Grooming) events. All members of the SCRUM Teams should participate to minimize communication issues.

The Nexus Guide (Page 6)

56
Q

Who is responsible for developing and integrating their work into an Increment?

A

All SCRUM Teams

The Nexus Guide (Page 10)

57
Q

What should be used during the Nexus Daily SCRUM to visualize and manage current dependencies?

A

The Nexus Sprint Backlog

The Nexus Guide (Page 7)

58
Q

Is implementing only parts of the Nexus methodology considered Nexus?

A

No - the result is not considered Nexus

The Nexus Guide (Page 10)

59
Q

Who makes up the Nexus Integration Team and what are they skilled at?

A
  • Software Professionals
  • Use of these practices, tools and general field of systems engineering.

The Nexus Guide (Page 6)

60
Q

What should serve both the overall effort of all SCRUM Teams in the Nexus and each individual team?

A

Events should be appended to, placed around, or replaced (in the case of the Sprint Review) regular SCRUM events to augment.

The Nexus Guide (Page 3)

61
Q

When referencing “Integration” (Example Nexus Integration Team) what is integration referencing?

A

Includes resolving any technical and non-technical cross-team constraints that may impede a Nexus’ ability to deliver a constantly Integrated Increment.

The Nexus Guide (Page 5)

62
Q

Who selects items from the refined Product Backlog for each team?

A

Representatives from each SCRUM Team.

The Nexus Guide (Page 4)

63
Q

In Nexus Sprint Planning what helps minimize communication issues?

A

All members of the SCRUM Teams should participate.

The Nexus Guide (Page 6)

64
Q

What helps minimize the emergence of new dependencies during Nexus Sprint Planning?

A

An adequately refined Product Backlog

The Nexus Guide (Page 7)

65
Q

What is the Product Owner responsible for?

A
  • Ordering & refining the Product Backlog
  • Maximum value is derived from the Integrated Increment created by the Nexus.

The Nexus Guide (Page 5)

66
Q

What is key to avoid conflict between the Nexus and SCRUM Teams?

A
  • Product Backlog items are adequately independent.
  • Worked on without excessive conflict between SCRUM Teams in a Nexus

The Nexus Guide (Page 8)

67
Q

What three areas does Nexus focus on for successful software development?

A
  • Organized and Sequenced
  • Dependencies resolved
  • Outcomes staged

The Nexus Guide (Page 2)

68
Q

When can the Increment truly be considered “Done”?

A

Only when usable and potentially releasable by the Product Owner.

The Nexus Guide (Page 10)

69
Q

If Integration issues exist what happens?

A

This information is transferred back to each SCRUM Team’s Daily SCRUM. SCRUM Teams then use their Daily SCRUM to create a plan for the day, being sure to address the integration issues raised during the Nexus Daily SCRUM.

The Nexus Guide (Page 4)

70
Q

How is the Nexus Sprint Backlog updated?

A

It is updated daily, often as part of the Nexus Daily SCRUM.

The Nexus Guide (Page 9)

71
Q

Is a Nexus SCRUM Master exclusive to the Nexus Team?

A

No - they can be part of a SCRUM Team as well.

The Nexus Guide (Page 6)

72
Q

What part of the Nexus Sprint Retrospective allows the Nexus as a whole to Adapt?

A

Opportunity for appropriate reps from the SCRUM Teams to meet again and agree on how to visualize and track identified actions.

The Nexus Guide (Page 8)

73
Q

What is the best description of the Nexus Sprint Review?

A

All Teams meet with the Product Owner to review the Integrated Increment. Adjustments may be made to the Product Backlog.

The Nexus Guide (Page 4)

74
Q

What 2 purposes does Product Backlog refinement serve?

A
  • Forecasts which team will deliver which Product Backlog item
  • It identifies dependencies across those teams.

The Nexus Guide (Page 8)

75
Q

How is the Product Backlog considered “Ready” for the Nexus Sprint Planning meetings?

A

When the Epics and Stories can be selected to be done by the SCRUM Teams with no or minimal dependencies with other SCRUM Teams.

The Nexus Guide (Page 9)

76
Q

What must be developed so that dependencies are detected and resolved before technical debt becomes unacceptable?

A

Software

The Nexus Guide (Page 10)

77
Q

Can the Composition of the Nexus Integration Team change over time? Why?

A

YesTo reflect the current needs of the Nexus

The Nexus Guide (Page 5)

78
Q

How are Product Backlog items that are reduced in granularity?

A

“Thinly Sliced” Functionality

The Nexus Guide (Page 9)

79
Q

What is the expected outcome from Software Automation Testing as a best practice for Software Practices?

A

It helps to manage the volume and complexity of the work and artifacts especially in scaled environments.

The Nexus Guide (Page 4)

80
Q

When is the Nexus Goal formulated?

A

In Nexus Sprint Planning

The Nexus Guide (Page 6)

81
Q

Why does the Nexus Sprint Review replace the individual SCRUM Team Sprint Reviews?

A

Because the entire integrated increment is the focus for capturing feedback from the stakeholders. It may not be possible to show all the completed work in detail.

The Nexus Guide (Page 7)

82
Q

What is the definition of the Nexus Goal?

A

It is the sum of all the work and Sprint Goals of the individual SCRUM Teams within the Nexus.

The Nexus Guide (Page 9)

83
Q

Does Nexus replace SCRUM Guidelines?

A

No - The Nexus Guide (Page 3)

84
Q

Complete this “The greater the complexity and dependencies, the more the Product Backlog item….”

A

“….must be refined to remove dependencies.”

The Nexus Guide (Page 8)

85
Q

Do Nexus teams use the same Product Backlog?

A

Yes -

The Nexus Guide (Page 3)

86
Q

What does the Nexus Goal describe?

A

The purpose that will be achieved by the SCRUM Teams during the Sprint.

The Nexus Guide (Page 6)

87
Q

What does a “Nexus” consist of?

A
  • Nexus Integration Team
  • Approximately 3 to 9 SCRUM Teams

The Nexus Guide (Page 5)

88
Q

When is the Nexus Sprint Review held?

A

At the end of the Sprint to provide feedback on the Integrated Increment that a Nexus has built over the Sprint.

The Nexus Guide (Page 7)

89
Q

What is the Nexus Sprint Backlog?

A

A composite of all Product Backlog items from the Sprint Backlogs of the individual SCRUM Teams.

The Nexus Guide (Page 9)

90
Q

Nexus Roles What is defined as “Exists to coordinate, coach, and supervise the application of Nexus and the operation of SCRUM so the best outcomes are derived?

A

The Nexus Integration Team

The Nexus Guide (Page 3)

91
Q

Should all teams maintain their individual Sprint Backlogs or defer to the single Product Backlog?

A

“All SCRUM Teams maintain their individual Sprint Backlogs.”

The Nexus Guide (Page 3)

92
Q

What is “Domain Knowledge”?

A

Knowledge that specific SCRUM Teams (of various business and computer systems) have. By assigning work to the specific SCRUM Team it minimizes interruptions between teams during a Sprint. (Expertise)

The Nexus Guide (Page 2)

93
Q

What does scaled development work require that individual SCRUM Teams may not frequently use?

A
  • Tools
  • Practices

The Nexus Guide (Page 6)

94
Q

In the Diagram what does 1 Represent?

A

Product BacklogThe Nexus Guide - Cover

The Nexus Guide (Page 10)

95
Q

How is the Nexus Sprint Backlog used?

A

To highlight dependencies and the flow of work during the Sprint.

The Nexus Guide (Page 9)

96
Q

What new role is added to Nexus that isn’t available to SCRUM Teams?

A

The Nexus Integration Team

The Nexus Guide (Page 3)

97
Q

Who ensures that practices and tools are implemented, understood and used to detect dependencies, and frequently integrate all artifacts to definition of “Done”?

A

The Nexus Integration Team

The Nexus Guide (Page 6)

98
Q

What is the Nexus Integration Team responsible for?

A

Successful Integration of all work by all SCRUM Teams in a Nexus.

The Nexus Guide (Page 5)

99
Q

Name the common activities the Nexus Integration Team might perform?

A
  • Coaching
  • Consulting
  • Highlighting Awareness of Dependencies & Cross-Team Issues.

The Nexus Guide (Page 5)

100
Q

What are the 3 key areas of focus in the “Refine the Product Backlog” Ceremony?

A
  • Decompose the Product Backlog to ID Dependencies and remove or minimize them.
  • Refine backlog items into thinly sliced pieces of functionality.
  • ID work as early as possible

The Nexus Guide (Page 4)

101
Q

At which Nexus Ceremony is the Integrated Increment inspected?

A

Nexus Sprint Review

The Nexus Guide (Page 9)

102
Q

Who is responsible for the Nexus definition of “Done”?

A

The Nexus Integration Team

The Nexus Guide (Page 10)

103
Q

Where is the Nexus Goal demonstrated?

A

The Nexus should show the functionality that they developed to achieve the Nexus Goal at the Nexus Sprint Review.

The Nexus Guide (Page 9)

104
Q

What key ceremony frequently integrates their work into a common environment that can be tested to ensure that the integration is done?

A

Development Work

The Nexus Guide (Page 4)

105
Q

Who attends the Nexus Daily SCRUM?

A

Appropriate representatives from the SCRUM Development Team.

The Nexus Guide (Page 4)

106
Q

When is Nexus Sprint Planning considered complete?

A

When each SCRUM Team has finished their individual Sprint Planning Events.

The Nexus Guide (Page 6)

107
Q

When scaling SCRUM what should be used to drive team organization?

A
  • Dependencies of Requirements
  • Domain Knowledge
  • Software Artifacts

The Nexus Guide (Page 3)

108
Q

What group takes control of integration issues?

A

The Nexus Integration Team.

The Nexus Guide (Page 5)

109
Q

Who is accountable for the Product Backlog, including its content, availability and ordering?

A

The Product Owner

The Nexus Guide (Page 9)

110
Q

For scalability what needs to be understood to a level where dependencies can be detected and minimized?

A

The Product Backlog

The Nexus Guide (Page 9)

111
Q

Does Nexus Sprint Planning remove the SCRUM Team Sprint Planning?

A

No - Once the overall work for the Nexus is understood, each SCRUM Team will perform their own separate Sprint Planning.

The Nexus Guide (Page 6)

112
Q

Is it just the integration team that adheres to the Nexus definition of “Done”?

A

No - All SCRUM Teams of a Nexus adhere to the definition.

The Nexus Guide (Page 10)

113
Q

Can individual SCRUM Teams choose to apply a more stringent definition of “Done” within their own teams beyond the Nexus definition of “Done”?

A

Yes - cannot apply LESS rigorous criteria than agreed for the Increment (Sprint).

The Nexus Guide (Page 10)

114
Q

In the Diagram what does 4 Represent?

A

Nexus Sprint RetrospectiveThe Nexus Guide - Cover

The Nexus Guide (Page 10)

115
Q

Define a Nexus Artifact?

A

Artifacts represent work or value to provide transparency and opportunities for inspection and adaption, as described in the SCRUM Guide.

The Nexus Guide (Page 9)

116
Q

What is defined as “A formal opportunity for a Nexus to focus on Inspection and adaption”?

A

The Nexus Sprint Retrospective

The Nexus Guide (Page 7)

117
Q

What are the 6 Nexus key Ceremonies (Nexus Process Flow)?

A
  • Refine the Product Backlog
  • Nexus Sprint Planning
  • Development work
  • Nexus Daily SCRUM
  • Nexus Sprint Review
  • Nexus Sprint Retrospective

The Nexus Guide (Page 4)

118
Q

How many SCRUM Teams are the basis for Nexus?

A

3 - 9

The Nexus Guide (Page 2)

119
Q

What artifact is formulated during Nexus Sprint Planning meeting?

A

The Nexus Goal

The Nexus Guide (Page 9)

120
Q

What should be used for the Nexus Integration Team to achieve resolution?

A

Bottom-up Intelligence

The Nexus Guide (Page 5)

121
Q

What is the purpose of Nexus Sprint Planning?

A

To coordinate the activities of all SCRUM Teams in a Nexus for a single Sprint.

The Nexus Guide (Page 6)

122
Q

Name the 3 dependencies that arise between the work of multiple teams at least every Sprint and may affect the “Done” defination.

A
  • Requirements
  • Domain Knowledge
  • Software and Test Artifacts

The Nexus Guide (Page 2)

123
Q

What artifact contains items that pass through different levels of decomposition from very large and vague requests to actionable work that a single SCRUM Team could deliver in a Sprint?

A

The Product Backlog

The Nexus Guide (Page 8)

124
Q

Nexus consists of what three items according to the Exoskeleton of scaled SCRUM graphic?

A
  • Roles
  • Artifacts
  • Events

The Nexus Guide (Page 3)

Scrum Nexus (1 decks)

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