Excellent video as always!!! Love your work!!!! One question regarding Nexus Sprint Planning? Does it replace the individual sprint planning for each team? Or do the teams have a separate planning session?
Thanks for the appreciation Poonam. 🙏 It depends. In some Nexus, individual teams wants to have their own Sprint Planning on top of the Nexus Sprint Planning. Ask the team, they're a self-managing team.
Excellent Explanation👍 So i have one query here in nexus we require the product managers as well or only one product owner can handle everything? just want more clarification here
Nexus does not require any product managers. The Product Owner can delegate the work (i.e detailing Product Backlog items) to others ... and if you have product managers, the Product Owner can delegate it to them.
hi Joshua, awesome explanation! Btw I have two questions, 1. Do you think nexus daily scrum to be done after team daily scrum or the other way around? and if there is a preferable order, what is the reason? I think based on the "Nexus Guide" : "Each Scrum Team’s Daily Scrum complements the Nexus Daily Scrum by creating plans for the day, focused primarily on addressing the integration issues raised during the Nexus Daily Scrum" It should be before right? 2. What is the preferable approach if we basically have multiple products and multiple scrum teams? Multiple nexus teams? And how if there are still some dependencies between those nexus teams? Thanks
Hi Adrian. 1. The Nexus Daily Scrum is held after the Daily Scrum as it requires delegates from each teams to bring obstacles from their team in relation to integration. 2. If you have multiple products that are dependent, you may want to reconsider the product structure as such the dependencies are non-existent or give access to each teams to the source code of components that they depend on. Amazon and Netflix does this. HTH.
Great explanation 🙏 How about the incident handling? What actions should be taken if the scrum team handle incidents along with the product backlog development?
It goes into their Sprint backlog and they have conversation with the Product owner as explained in this video ua-cam.com/video/VltdPhzsvxo/v-deo.html&lc
Heyy, I have two queries here- 1- In Nexus framework what should be the sprint duration because here multiple teams are working, in Scrum the 1 week is the minimum and 4 week is the maximum sprint duration…but in nexus we work in a broader way so in general 3 or 4 week sprint we prefer? or it depends 2- I am thinking that in Nexus framework we need to manage the Nexus sprint backlog, Individually Team’s Sprint Backlog and we manage things at team level along with the nexus level( like daily scrum etc) Will it make things complex?
It is possible that in a Nexus several teams running different Sprint cadence. It's more complex. Technical / DevOps practice need to be further emphasised in this scenario to ensure there is always an integrated increment. The Nexus Sprint Backlog is made visible to everyone in Nexus as it visualise the dependencies between the work for each team. And yes each individual Scrum team manage their own Sprint Backlog.
Uniform cadence is less complex but it doesn't have to ... _self-managing team_ rule applies here. The cadence for each team can be discussed during Nexus Retrospectives. Every time one or more Scrum teams found ineffectiveness, discuss it during retrospectives.
![Metrics 📈 For Measuring The Scrum Team's Effectiveness [Don’t Use Velocity]](http://i.ytimg.com/vi/2AzDzX0xaJE/mqdefault.jpg)
Neatly explained in fewer than 15 minutes! I'm going to recommend this video to people who quickly want to learn more about Nexus.
Thanks for all your help Jesse.
Really complete explanation 👍🏼. Thank you for sharing 🖖🏼
Dude, you're awesome :) Well deserved like and comment!
Thanks for the appreciation and thanks for watching mate. Keep improving. :)
Thanks, this is really helpful, especially the graphics!
Thanks Michael 🙏
Excellent video as always!!! Love your work!!!!
One question regarding Nexus Sprint Planning?
Does it replace the individual sprint planning for each team? Or do the teams have a separate planning session?
Thanks for the appreciation Poonam. 🙏 It depends. In some Nexus, individual teams wants to have their own Sprint Planning on top of the Nexus Sprint Planning. Ask the team, they're a self-managing team.
@@scrummasterinblack Thank you !!!
Excellent Explanation👍
So i have one query here in nexus we require the product managers as well or only one product owner can handle everything? just want more clarification here
Nexus does not require any product managers. The Product Owner can delegate the work (i.e detailing Product Backlog items) to others ... and if you have product managers, the Product Owner can delegate it to them.
@@scrummasterinblack ok, so here in nexus only one product owner is there? or multiple product owner can also exists
@@anuragverma1720 as mentioned in the video, one product one Product Owner. Just like one company only have one CEO.
@@scrummasterinblack Great, Thank You Very Much🙂
nice punch line to finish
thanks for stopping by Olivier ✌️
hi Joshua, awesome explanation!
Btw I have two questions,
1. Do you think nexus daily scrum to be done after team daily scrum or the other way around? and if there is a preferable order, what is the reason?
I think based on the "Nexus Guide" :
"Each Scrum Team’s Daily Scrum complements the Nexus Daily Scrum by creating plans for the day, focused primarily on addressing the integration issues raised during the Nexus Daily Scrum"
It should be before right?
2. What is the preferable approach if we basically have multiple products and multiple scrum teams? Multiple nexus teams? And how if there are still some dependencies between those nexus teams?
Thanks
Hi Adrian.
1. The Nexus Daily Scrum is held after the Daily Scrum as it requires delegates from each teams to bring obstacles from their team in relation to integration.
2. If you have multiple products that are dependent, you may want to reconsider the product structure as such the dependencies are non-existent or give access to each teams to the source code of components that they depend on. Amazon and Netflix does this.
HTH.
Thanks Joshua for the clear explanation 🙏🙏
Great explanation 🙏
How about the incident handling? What actions should be taken if the scrum team handle incidents along with the product backlog development?
It goes into their Sprint backlog and they have conversation with the Product owner as explained in this video ua-cam.com/video/VltdPhzsvxo/v-deo.html&lc
Heyy, I have two queries here-
1- In Nexus framework what should be the sprint duration because here multiple teams are working, in Scrum the 1 week is the minimum and 4 week is the maximum sprint duration…but in nexus we work in a broader way so in general 3 or 4 week sprint we prefer? or it depends
2- I am thinking that in Nexus framework we need to manage the Nexus sprint backlog, Individually Team’s Sprint Backlog and we manage things at team level along with the nexus level( like daily scrum etc)
Will it make things complex?
It is possible that in a Nexus several teams running different Sprint cadence. It's more complex. Technical / DevOps practice need to be further emphasised in this scenario to ensure there is always an integrated increment.
The Nexus Sprint Backlog is made visible to everyone in Nexus as it visualise the dependencies between the work for each team. And yes each individual Scrum team manage their own Sprint Backlog.
@@scrummasterinblack : Thank You for your explanation, eagerly waiting for your next vedios🙂
Should the Sprints of the scrum teams all start at the same time?
Uniform cadence is less complex but it doesn't have to ... _self-managing team_ rule applies here. The cadence for each team can be discussed during Nexus Retrospectives. Every time one or more Scrum teams found ineffectiveness, discuss it during retrospectives.
How do you scale Scrum beyond ten team members with Nexus?