8 Tips for Scrum Masters to Improve Cross-Team Refinement in 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.
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.