1484244826 by Unknown

1484244826 by Unknown

Language: eng
Format: epub
Published: 2019-04-24T13:45:06+00:00

Chapter 3 IntroduCtIon to SCrum and agIle ConCeptS

• Artifacts: All Scrum teams use the same, single product

backlog. As the PBIs are refined and made ready,

indicators of which team will do the work inside a

sprint are made visual. A new artifact, the Nexus sprint

backlog, exists to raise this transparency during the

sprint. All Scrum teams maintain their individual sprint


• Events: Events are appended to, placed around, or

replace (in the case of the sprint review) 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. Backlog refinement has become

a proper event as well. This is an important practice for

single teams, but at scale it becomes mandatory.

Figure 3-18. The Nexus framework (nexusguide.org)

All work in a Nexus may be done by all members of the Scrum teams

as cross-functional members of the Nexus. Based on dependencies, the

teams may select the most appropriate members to do specific work.


Chapter 3 IntroduCtIon to SCrum and agIle ConCeptS

• Refine the product backlog: The product backlog needs to be decomposed so that dependencies are identified

and removed or minimized. PBIs are refined into thinly

sliced pieces of functionality, and the team likely to do

the work is identified as early as possible.

• Nexus sprint planning: Appropriate representatives

from each Scrum team meet to discuss and review

the refined product backlog. They select PBIs for each

team. Each Scrum team then plans its own sprint,

interacting with other teams as appropriate. The

outcome is 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

sprint backlog makes the Scrum team's selected PBIs,

and any dependencies, transparent.

• Development work: All teams develop software,

frequently integrating their work into a common

environment that can be tested to ensure the

integration is done.

• Nexus daily Scrum: Appropriate representatives from each Scrum development team meet daily to indicate

whether any integration issues exist. If identified,

this information is transferred back to each Scrum

development team’s daily Scrum. Scrum development

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.

• Nexus sprint review: All teams meet with the

appropriate stakeholders to review the integrated

increment. Stakeholder feedback may result in

adjustments to the product backlog.



Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.