
The Nexus Daily Scrum is the scaled version of the Daily Scrum event from the Scrum framework.
How does it work?
Attendees at this event inspect the current state of the integrated Increment and seek to identify newly discovered integration issues or cross-team dependencies.
Where issues are identified, individual Scrum Teams will then take ownership to address the underlying problems. As with the Daily Scrum, it is expected that attendees at the Nexus Daily Scrum will self-manage to find the best ways to make effective use of this event.
During the Nexus Daily Scrum, possible topics for discussion could be:
- Was the previous day’s work successfully integrated? If not, why not?
- What new dependencies have been identified?
- What information needs to be shared across teams in the Nexus?
The Nexus Sprint Backlog should be used to visualise and manage integration issues and dependencies that have been identified.
Who should attend?
Appropriate representatives from the Scrum Teams attend the Nexus Daily Scrum.
The Scrum Teams will decide who is the right person or people to attend this event. As with all things in Scrum, inspection and adaption may lead to the attendees to this event changing over time.
A Scrum Master may facilitate this event and help the team to self-manage as requested or required. A Product Owner may also attend if their presence is helpful to the team. Sometimes the discussions in this event will not prove interesting to a Product Owner as they will involve high levels of technical detail.
What is the timebox?
The Nexus framework does not mandate a time box for the Nexus Daily Scrum. This is deliberate as depending on the number of teams in the Nexus, number of attendees at the Nexus Daily Scrum and level of integration and dependency issues being handled, the time required may vary between organisations.
The Nexus framework does suggest that the duration of Nexus events be guided by the length of the corresponding events in the Scrum framework. So for the Nexus Daily Scrum, the target for the timebox would be 15 minutes. However, Inspection and adaption may lead to this being adjusted over time as required.
When and where does it take place?
As with the Daily Scrum, the Nexus Daily Scrum should be held at a consistent time and place to ensure attendees have a clear expectation of when and where they need to be.
What else do I need to know?
Just because the Nexus Daily Scrum mandates a meeting between members of the various Scrum Teams, they can and should meet at other times as appropriate to deal with integration issues that emerge during development. Impediments shouldn’t be queued for discussion at this event. The Nexus Daily Scrum is the latest time any shared issues should be raised.
The Nexus Daily Scrum replaces the earlier concept of a Scrum of Scrums that was widely used to discuss issues and dependencies when multiple Scrum teams worked on a single product. The Nexus Integration team also takes on many of the responsibilities that would previously have been taken on by representatives at the Scrum of Scrums.
Next post: Nexus Sprint Review –>
<– Previous post: Nexus Sprint Planning
Index – Scaled Professional Scrum And Nexus – The Definitive Guide





Where does it say in Nexus Guide, that possible topics of discussion would be:
Was the previous day’s work successfully integrated? If not, why not?
What new dependencies have been identified?
What information needs to be shared across teams in the Nexus?
It doesn’t. Hence “During the Nexus Daily Scrum, possible topics for discussion could be”
Hello Simon – i have quick question for you
Under what is time box you mentioned, ‘The Nexus framework does not mandate a time box for the Nexus Daily Scrum.”
where nexus guide says “Nexus Events -The duration of Nexus events is guided by the length of the corresponding events in the Scrum Guide. They are time-boxes in addition to their corresponding Scrum events.”
You also mention the target should be 15 minute which is driven by scrum framework. Is first line not contradicted the nexus guide? Want to understand what do you mean when you say it is not mandated a little bit more?
Hi Rinku,
“Guided by” is a recommendation rather than a rule. So it may be a good idea for Nexus Daily Scrum to be < 15 mins but it may not be possible so Nexus stops short of mandating this. The suggestion is though to keep it short and focussed like the Daily Scrum and aim for the same or similar time box. Regards Simon
Thanks for Quick response Simon, Understood and i was just little confused with the below statement so i hope this is not a correct statement in context to nexus daily scrum?
“The Nexus framework does not mandate a time box for the Nexus Daily Scrum”
Perhaps if I state it a different way it will be a little clearer:
The Nexus Daily Scrum will have a time-box, but the size of that time-box is not mandated by Nexus.
Thanks ,it helps
can you please help with below clarification
Does this mean all the event are just guided and does not have a time box unlike scrum? Also second part says ‘They are time-boxes in addition to their corresponding Scrum events.’ so can you explain this a bit too?
The Nexus events will have a time-box, but Nexus does not mandate the length of the time-box.