GuideRolesEventsWorkflow

Nexus Events

Cross-Team Refinement

Cross-Team Refinement is where dependency reduction happens. The Product Backlog must be understood at a level where dependencies can be detected and minimized. Teams refine together for items that span multiple teams, and independently for team-specific items.

Dependency reduction · Timebox: ~10% of Sprint capacity

Overview

Cross-Team Refinement is where dependency reduction happens. The Product Backlog must be understood at a level where dependencies can be detected and minimized. Teams refine together for items that span multiple teams, and independently for team-specific items.

Event Ownership

Owned / Facilitated By
Product Owner (priority guidance) / NIT (dependency detection) / Teams (refinement work)
PO ensures top items are being refined with dependency information visible
NIT facilitates cross-team refinement sessions for items that involve multiple teams
Teams do the actual refinement: understanding, estimating, splitting, and dependency analysis
NIT coaches teams on identifying and designing away dependencies during refinement

Who Should Be Present

Cross-Team Refinement
Representatives from teams that will likely work on related items. PO provides priority context. NIT guides dependency analysis
Single-Team Refinement
One team refining items specific to their upcoming work. Standard Scrum backlog refinement
Product Owner
Available for priority questions. Ensures refined items have dependency indicators for Sprint Planning
NIT Members
Facilitate dependency detection. Help teams identify integration strategies and item decomposition that reduces coupling

Preparation Checklist

01PO: Identify items needing cross-team refinement in upcoming 2–3 Sprints
02NIT: Analyze recent dependency patterns to focus refinement on high-risk areas
03Teams: Review items before refinement sessions
04NIT: Prepare cross-team refinement facilitation materials

Facilitation Techniques

Click any technique to expand details and learn when to apply it.

Dependency Detection Workshop

For each top-priority item, teams map which other teams’ code, APIs, or domain knowledge it touches. Color-code by severity: red (hard dependency), yellow (coordination needed), green (independent). Design away reds first.

Click to expand

Item Splitting for Independence

When an item creates dependencies, explore decomposition strategies that make resulting items independent. Can the item be split vertically so each team delivers independently? Can an interface contract be defined upfront?

Click to expand

Tips & Tricks

01
The primary goal of cross-team refinement is dependency reduction, not just understanding
02
Invest ~10% of Sprint capacity in refinement — this is the highest-leverage activity for scaling
03
If Sprint Planning consistently surfaces surprise dependencies, refinement isn’t happening early enough
04
Track dependency count per Sprint over time. Decreasing dependencies signal improving Nexus health
05
Cross-team refinement is where architecture decisions get made — involve people with system-level perspective
06
Dependency Trend Tracking
Track the number and severity of cross-team dependencies per Sprint. Share this data at the Nexus Sprint Retrospective. A downward trend validates that refinement and architecture improvements are working.

Success Takeaways by Role

What each participant should walk away with when this event is run well.

Teams

Deep understanding of upcoming work and its cross-team implications; confidence in Sprint Planning readiness

Product Owner

Product Backlog items with dependency information; items ready for prioritization

NIT

Dependency landscape mapped; integration strategies identified; coaching opportunities for teams

Goal

Items refined to a level where dependencies are visible and minimized

Goal

Teams understand cross-team implications of upcoming work

Goal

Dependency indicators attached to Product Backlog items for Sprint Planning

Goal

Items decomposed to reduce cross-team coupling where possible