GuideRolesEventsWorkflow

Nexus Events

Nexus Daily Scrum

The Nexus Daily Scrum is a daily event where representatives from each team meet to identify integration issues and cross-team dependencies discovered since the last sync. It’s not a status meeting — it’s focused exclusively on cross-team concerns. Teams then hold their own Daily Scrums.

Cross-team coordination · Timebox: ≤15 minutes

Overview

The Nexus Daily Scrum is a daily event where representatives from each team meet to identify integration issues and cross-team dependencies discovered since the last sync. It’s not a status meeting — it’s focused exclusively on cross-team concerns. Teams then hold their own Daily Scrums.

Event Ownership

Owned / Facilitated By
NIT Scrum Master (facilitates) / Team Representatives (drive content)
NIT SM facilitates the Nexus Daily Scrum, keeping it focused on cross-team issues
Team representatives surface integration blockers, dependency status, and coordination needs
Issues identified are taken back to individual team Daily Scrums for action
NIT members help resolve integration issues identified during the sync

Who Should Be Present

Team Representatives
One or more members per team. Report on cross-team dependencies, integration status, and blockers affecting other teams
NIT Scrum Master
Facilitates the sync, ensures focus on integration issues, tracks action items
NIT Members
Available to help resolve integration issues surfaced during the sync

Preparation Checklist

01Representatives review their team’s integration status and cross-team dependencies
02Check CI/CD pipeline and integration test results for cross-team failures
03Review the Nexus Sprint Backlog for dependency status updates

Facilitation Techniques

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

Integration-Focused Questions

Three questions adapted for cross-team context: What did my team integrate yesterday? What will we integrate today? What cross-team issues are blocking integration? This keeps the focus on integration, not general status.

Click to expand

Walk the Nexus Sprint Backlog

Walk through cross-team items from right to left (nearest to Done first). For each item, ask: ‘Is integration on track? Are there blockers?’ Skip items with no cross-team concerns.

Click to expand

Red/Green Integration Dashboard

Start each Nexus Daily Scrum by showing the CI/CD pipeline dashboard. Green builds need no discussion. Red builds become the agenda. This uses objective data to drive the conversation.

Click to expand

Tips & Tricks

01
15 minutes maximum — this is cross-team coordination, not a status meeting
02
Not everything needs discussion. Only cross-team integration issues and dependency updates belong here
03
Representatives bring insights back to their team’s Daily Scrum — the two events are connected
04
If the Nexus Daily Scrum consistently has nothing to discuss, dependencies are well-managed
05
If it consistently runs over, there are too many dependencies — fix the root cause
06
Immediate Follow-Up Conversations
Issues requiring more than 30 seconds of discussion should be taken offline immediately after the Nexus Daily Scrum with only the relevant people. Don’t let the sync become a problem-solving meeting.

Success Takeaways by Role

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

Team Representatives

Awareness of cross-team issues to bring back to their teams; coordination agreements for the day

NIT

Pulse on integration health; issues to help resolve; data on dependency management effectiveness

Goal

Surface cross-team integration issues immediately

Goal

Update dependency status from the Nexus Sprint Backlog

Goal

Identify blockers that affect multiple teams

Goal

Create actionable coordination plans for the day

Cross-Framework Definition
See Nexus Daily Scrum in the glossary
→