www.scrum.org Open in urlscan Pro
35.169.77.29  Public Scan

Form analysis
2 forms found in the DOM

GET /search/node

<form action="/search/node" method="get" id="search-block-form" accept-charset="UTF-8" data-drupal-form-fields="edit-keys">
  <div class="form-item form-group form-type-search form-item-keys form-no-label">
    <input title="Enter the terms you wish to search for." data-drupal-selector="edit-keys" type="search" id="edit-keys" name="keys" value="" size="20" maxlength="128" placeholder="Search" class="form-search form-type- form-control">
  </div>
  <div data-drupal-selector="edit-actions" class="form-actions js-form-wrapper form-wrapper" id="edit-actions">
    <input data-drupal-selector="edit-submit" type="submit" id="edit-submit" value="Search" class="button js-form-submit form-submit form-type- form-control">
  </div>
</form>

POST /resources/blog/8-tips-scrum-masters-improve-cross-team-refinement-nexus?destination=/resources/blog/8-tips-scrum-masters-improve-cross-team-refinement-nexus%3Futm_source%3Dnewsletter%26utm_medium%3Demail

<form class="user-login-form" data-drupal-selector="user-login-form"
  action="/resources/blog/8-tips-scrum-masters-improve-cross-team-refinement-nexus?destination=/resources/blog/8-tips-scrum-masters-improve-cross-team-refinement-nexus%3Futm_source%3Dnewsletter%26utm_medium%3Demail" method="post" id="user-login-form"
  accept-charset="UTF-8" data-drupal-form-fields="edit-name,edit-pass,edit-submit--2">
  <div class="form-item form-group form-type-textfield form-item-name">
    <label for="edit-name" class="js-form-required form-required">Email address</label>
    <input autocorrect="none" autocapitalize="none" spellcheck="false" data-drupal-selector="edit-name" type="text" id="edit-name" name="name" value="" size="15" maxlength="60" placeholder="email address"
      class="form-text required form-type- form-control" required="required" aria-required="true">
  </div>
  <div class="form-item form-group form-type-password form-item-pass">
    <label for="edit-pass" class="js-form-required form-required">Password</label>
    <input data-drupal-selector="edit-pass" type="password" id="edit-pass" name="pass" size="15" maxlength="128" placeholder="password" class="form-text required form-type- form-control" required="required" aria-required="true">
  </div>
  <input autocomplete="off" data-drupal-selector="form-jh-ejmf-929qqpvoxbchl8oix3pqvt9fqbhif29idbs" type="hidden" name="form_build_id" value="form-Jh-ejMF-929qqPVoXbcHl8oix3pQVT9fQbhIf29idBs" class="form-type- form-control">
  <input data-drupal-selector="edit-user-login-form" type="hidden" name="form_id" value="user_login_form" class="form-type- form-control">
  <div data-drupal-selector="edit-actions" class="form-actions js-form-wrapper form-wrapper" id="edit-actions--2">
    <input data-drupal-selector="edit-submit" type="submit" id="edit-submit--2" name="op" value="Go" class="button js-form-submit form-submit form-type- form-control">
  </div>
</form>

Text Content

Skip to main content
Home
X
 * login
 * register
 * partners
 * support
 * Search

 * Home
 * About Us
   * Back
   * About Us
   * Overview
   * Why Scrum.org
   * News
   * Diversity & Social Responsibility
   * Meet Our Staff
   * Meet Our Trainers & Coaches
   * Contact Us
   * Careers
 * Training
   * Back
   * Training
   * Overview of Courses
   * View Class Schedule
   * Request a Private Class
   * Find a Trainer or Coach
   * Become a Professional Scrum Trainer
   * Students Reviews & Feedback
   * Professional Scrum Competencies
 * Certification
   * Back
   * Certification
   * Overview
   * Professional Scrum Master
   * Professional Scrum Product Owner
   * Professional Scrum Developer
   * Scaled Professional Scrum
   * Professional Scrum with Kanban
   * Professional Agile Leadership
   * Professional Agile Leadership - Evidence-Based Management
   * Professional Scrum with User Experience
   * Search Professional Scrum Certificate Holders
 * Open Assessments
   * Back
   * Open Assessments
   * Overview
   * Scrum Open
   * Product Owner Open
   * Scrum Developer Open
   * Nexus Open
   * Scrum with Kanban Open
   * Agile Leadership Open
   * Evidence-Based Management Open
 * Community
   * Back
   * Community
   * Blog
   * Forum
   * Meetups
   * Events
   * Join the Community
   * Search Professional Scrum Certificate Holders
 * Resources
   * Back
   * Resources
   * View All Resources
   * What is Scrum?
   * ...for Scrum Masters
   * ...for Product Owners
   * ...for Software Developers
   * ...for Leaders
   * The Scrum Guide
   * Scaling Scrum with Nexus
   * Scrum with Kanban
   * Evidence Based Management (EBM)
   * Webcasts
   * Videos
   * Case Studies



X
Back
X


LOGIN

Email address
Password

 * Forgot Password


NOT REGISTERED?

If you don't already have a Scrum.org account, you can sign up in just a few
seconds.

Register Here

Subscribe to our blog by signing up for the Scrum.org newsletter, or by
subscribing to the RSS feed.

 RSS
Back to Blog Listing Prev Next
August 3, 2021


8 TIPS FOR SCRUM MASTERS TO IMPROVE CROSS-TEAM REFINEMENT IN NEXUS

Simon Flossmann

Simon Flossmann website Simon Flossmann Twitter Simon Flossmann LinkedIn Simon
Flossmann contact View profile


5 from 1 rating
0 Comments
Scaled Scrum Nexus

Reducing dependencies is expensive.

How effectively a Nexus works depends on its ability to eliminate dependencies.
Eliminating dependencies simplifies integration. Scrum Masters who efficiently
perform cross-team refinements save time. Saving time saves money. 

8 Tips on how Scrum Masters can improve Cross-Team Refinement and thereby save
the Nexus time.

 


FEATURE BAZAR: SCRUM TEAMS PITCH WHICH PRODUCT BACKLOG ITEMS THEY WANT TO WORK
ON

 

At a Feature Bazar, the Product Owner presents the new features. Afterward, the
teams select the topics they want to work on. Each feature should be chosen by
at least two teams. By assigning teams to the features, the initial overview for
the Cross-Team Refinement is quickly created. 

 


UPDATE THE CROSS-TEAM REFINEMENT BOARD DAILY

 

Just as the Nexus Sprint Backlog is updated daily in the Nexus Daily Scrum when
new dependencies occur in the current Sprint, the Cross-Team Refinement Board
should also be updated daily. Only when the Cross-Team Refinement Board
represents a real-time picture of all known dependencies, is it easy for the
teams to resolve them.

 

The Nexus updates the Cross-Team Refinement Board daily. Image by Richard
Hundhausen. 


REPRESENTATIVES OF THE TEAMS PARTICIPATE IN THE CROSS-TEAM REFINEMENT

 

Inviting all members of the Scrum teams to the Cross-Team Refinement is often
neither practical nor necessary. In order to proceed in a focused manner, only
representatives of the individual teams should be invited. Scrum teams select
their representatives based on the work to be refined. Domain and technical
knowledge are good selection criteria to quickly identify appropriate team
members. 

 


ALTERNATE TEAM AND CROSS-TEAM REFINEMENT

 

In cross-team refinement, cross-team dependencies are uncovered, eliminated, and
forecasts are made about which team is likely to work on which Product Backlog
item. In contrast, in team refinement, Product Backlog items are broken down,
detailed, and estimated. Often, new cross-team dependencies are found in the
team refinement. To eliminate these dependencies as quickly as possible, it
makes sense to constantly alternate team and cross-team refinement. 

 


CROSS-TEAM REFINEMENT SHOULD BE A REGULAR MEETING

 

To reduce unnecessary scheduling, cross-team refinement should always take place
on the same date. For me, it has proven successful to reserve at least one
afternoon a week for the Cross-Team Refinement.

 


NOT JUST VISUALIZE DEPENDENCIES, BUT ELIMINATE THEM 

 

Visualizing dependencies in the Nexus Sprint Backlog to make them transparent is
only the first step. The critical step is to consistently eliminate dependencies
between teams. Ways to eliminate dependencies are: Interchange features between
teams, break down Product Backlog items, build up missing knowledge in the team
and change the likely possible processing order.


 


NEXUS INTEGRATION TEAM PROVIDES AWARENESS OF CROSS-TEAM DEPENDENCIES

 

In their daily teamwork, Nexus Integration Team members constantly keep an eye
out for potential dependencies. If new dependencies are discovered, they
encourage team members to make them transparent at the Cross-Team Refinement
Board and look for ways to eliminate them early. In the long run, this creates
awareness of the impact of cross-team dependencies within the teams. 

 


DON'T FALL INTO THE WATERFALL TRAP: DON'T PLAN TOO FAR IN ADVANCE, FOCUS ON THE
NEXT SPRINT

 

Software development is complex. There are unknown unknowns. Therefore, it is
impossible to anticipate all dependencies in advance, no matter how long
refinement and planning are done. To avoid wasting time, the nexus should only
refine the next one to three sprints in advance. 

 

Trying to anticipate the implementation sequence of the Product Backlog is like
a faucet: the further we turn it on, the closer we are to the waterfall. 

 


WANT TO LEARN MORE?

 

Hopefully, this article was useful for you. Cross-Team Refinement is one of the
many interesting topics that is covered in the Scaled Professional Scrum course.
If you’d like to join the Scaled Professional Scrum course, check out my class
schedule page for more information.


SHARE THIS POST

 * Email
 * Facebook
 * Twitter
 * LinkedIn
 * Reddit
 * Pocket

Scaled Scrum Nexus
Blog Comments

Prev Next

© 2021 

Scrum.org. All Rights Reserved.
 * Contact
 * Privacy
 * Terms of Service
 * TM and © Guidelines

 * https://twitter.com/Scrumdotorg
 * http://facebook.com/scrum.org
 * https://www.linkedin.com/company/scrum-org
 * https://www.youtube.com/user/Scrumorg

By using this site you are agreeing to the Privacy Policy and Terms of Service.X