How To Scale Scrum for Large Software Teams | The Nexus Framework from Scrum.org
ฝัง
- เผยแพร่เมื่อ 15 มี.ค. 2016
- tv.ssw.com/6673/scale-scrum-la... In this video SSW Chief Architect Adam Cogan sits down with Scrum.org Team Member Steve Porter.
They walk through the new Nexus Framework, an Agile framework designed for large scale software development.
-------------------------------------------------------------------------------
Like and subscribe if you enjoyed this content.
Want more great videos? Check out tv.ssw.com.au
Facebook: / ssw.page
Twitter: / ssw_tv - วิทยาศาสตร์และเทคโนโลยี
I finally understood the role of the Nexus Intergration Team. Thanks for sharing!
Good video - to add, the definition of NIT as a Scrum Team has been changed a wile ago - it is now simply defined as a group of representatives from all teams, without any Scrum roles like PO, SM or such. Thanks again for this overview !
Thanks for the video. The Nexus was explained in an easy way to understand.
Very good explanation, thanks!
The version they are looking at on the table is an older version. Look closely at the NIT and where it points. It's different than what it shows today.
Great video, thanks guys. I wish you spoke a little bit about the refinement of the backlog, as it is also a pretty important part in Nexus.
You can get those details from any other well-made Video on Scrum in general :)
Hey there, thanks for the Video. Where can I find the mentioned "cartoon about nexus" ?
So it's scrum, but for every meeting we have meeting to plan the meeting and in some cases a third meeting to relay what was said in the previous meeting to people who weren't there? All this did was double the number of meetings. Unless your a VP or some product person I don't see anyone wanting to deal with this. Seems painful. How do you have all of these meetings and actually still have time to do sprint work, is the assumption that you'll need longer sprints? How does this account for teams in the same Nexus with different working schedules like distributed teams?
Good presentation but what I am missing is this note: People in the NIT team can also be a part of the individal teams (double roll). Important here is that the work in the NIT team goes first and their work in the individual team comes second.
There was initially a model where the NIT needed to be a Scrum Team, but it has been dropped, so far as I know.
Great video, sound is really bad though
So how the time of 15 mins of daily scrum will be divided in all the scrum teams in daily stand up meeting?
Each Scrum team has it's own daily scrum, separate from any other Scrum team.
Inside each team, the members of that team use no more than 15 minutes total to talk about their progress/plans/impediments.
Ulysses Maclaren www.ssw.com.au
I may know this. Just wanted to confirm. So there is no sprint review in nexus? I believe , from the video and the guide, the nexus sprint review eliminates the need of individual sprint review. Confirm please ?
Correct. You do not have individual Sprint Reviews anymore. You do however have 1 cohesive Nexus Sprint Review where they all come together and show their complete work to the stakeholders.
Do Nexus integration team have some SPIs to work with? or their job is to make sure that Nexus Sprint Backlog Items are well built and integrated, in other words the Nexus Sprint Backlog is their Sprint Backlog?
2ndly, what is the role of Product Owner in Nexus Integration team? Making sure that Nexus Sprint Backlog Items are well built and integrated, right in the shape of expected outcome of Nexus Sprint Backlog item???
3rdly, how the Product Owners? and Scrum Masters of each Scrum teams work together???
can I answer?
@@dd21 yes!;-) I would be very interested in your answers!
How many *SPRINT BACKLOGs* will be there?
Just one product backlog, and the different teams will pull out different PBIs into their own sprint backlogs (one sprint backlog per team)
Ulysses Maclaren www.ssw.com.au