No mention of team structures increasing/decreasing dependencies; in practice, you have one PO for several teams? Im guessing the features are very high-level.... what happens when teams fail to communicate and manage their dependencies and technical designs? some teams are plain poor at self management and organisation.
In normal single team Scrum the entire team usually sits together with the PO during sprint planning to all pitch in on how long they think each user story is going to take to implement and they all have to agree and commit to being able to finish the agreed work in upcoming sprint, but if I understand correctly in LeSS only a single representative from each team has to agree to the work their entire team will need to do in the upcoming sprint without consulting the other team members of their team. How does this not cause problems of over committing if the entire team isn't in on the committing phase?
Hi Morten, In LeSS, it is up to the teams on how they are doing this. It can be representatives in Sprint Planning 1 or it is the whole team. That said, in Scrum and LeSS, there is no "team committing" and there are no User Stories. User Stories have never been part of Scrum and team committing for Sprint was removed a couple years ago.
LeSS does not prescribe whether the entire team ought to be there or a team representative. In LeSS (and Scrum), teams do not commit and in Sprint Planning 1, the teams together discuss on how much they think the teams can do and how these items are distributed over the teams. Personally, I've never experienced problems with that :)
Hi, thank you great presentation, I have 2 questions. 1) what is the learning path to learn this scaled agile framework? 2) what is the best training provider for LesS? is there any qualification for LeeS?
Hi Lotfy! I think for these questions, it is best to check out the less.works site. The most common course for learning more about LeSS is the "Certified LeSS Practitioner" course. The best training provider probably depends on your taste and geographical location. Hope that helps!.
How it is different from Scrum depends a lot on your Scrum Trainer (unfortunately). In short, Scrum is described, focused as one team. "Fractal Scrum," Scrum of Scrums, Scrum@Scale, and "copy-paste Scrum" means trying to copy team-scrum through the organization. LeSS tries to apply single-team Scrum with not just one-team working on the product but multiple teams working on the same Product (hence one PO and one PBL). I recommend reading more about it in the LeSS Book.
Smells like Scaled Agile with different terms. Hater: "I hate SAFe! I'll make something new and call it LeSS... with all the same things but new names." That's all this is.
Haha! Believe me, LeSS is the virtual opposite of SAFe. Neither is it new as it is around for about the same time, perhaps longer. I guess it never had enough shine, polish and roles to be the same attractive to organizations.
@@paulstasiak8482 Uhm, no. The whole concept of PI doesn't exist in LeSS. SP1 is just for 1 Sprint (usually 2 weeks) and typically lasts about... 30 minutes. Since PI doesn't exists, so doesn't do PI Retro. "Demos" don't exists either. There is a Sprint Review but the purpose is not to "demo" things but to talk about what you are going to build next based on what the teams did the previous Sprint (usually 2 weeks)
I am giving my presentation on LESS tomorrow and as I dont have much time, i referred to this video. Its amazing, I would recommend. Thnx.
Nice one, with an amazing visualization!
Concepts pretty easy to follow. Thank you
Very nice description.
It was nice to underestand this. One suggestion: You need to be more slow while speaking everyone cant follow same speed.
and drop the pen/drawing animations.
Thanks Himanshu. In case this helps anyone, Dawson read it a bit slower here: czcams.com/video/1BZf_Oa7W94/video.html .
@@delvallo9652 I agree. I'm making the new videos without the pen/drawing gimmick now.
@@MichaelJamesSeattle where can I find the gimmick free version?
@@MichaelJamesSeattle I found the drawings remarkably good, and they helped me process the information. I guess I'm a visual learner.
hello, please can you tell me which whiteboard drawing software did you use to create this video? thank you!
We used a 3rd party vendor for this.
No mention of team structures increasing/decreasing dependencies; in practice, you have one PO for several teams? Im guessing the features are very high-level.... what happens when teams fail to communicate and manage their dependencies and technical designs? some teams are plain poor at self management and organisation.
In normal single team Scrum the entire team usually sits together with the PO during sprint planning to all pitch in on how long they think each user story is going to take to implement and they all have to agree and commit to being able to finish the agreed work in upcoming sprint, but if I understand correctly in LeSS only a single representative from each team has to agree to the work their entire team will need to do in the upcoming sprint without consulting the other team members of their team.
How does this not cause problems of over committing if the entire team isn't in on the committing phase?
Hi Morten,
In LeSS, it is up to the teams on how they are doing this. It can be representatives in Sprint Planning 1 or it is the whole team.
That said, in Scrum and LeSS, there is no "team committing" and there are no User Stories. User Stories have never been part of Scrum and team committing for Sprint was removed a couple years ago.
LeSS does not prescribe whether the entire team ought to be there or a team representative. In LeSS (and Scrum), teams do not commit and in Sprint Planning 1, the teams together discuss on how much they think the teams can do and how these items are distributed over the teams.
Personally, I've never experienced problems with that :)
Hi, thank you great presentation, I have 2 questions. 1) what is the learning path to learn this scaled agile framework? 2) what is the best training provider for LesS? is there any qualification for LeeS?
Hi Lotfy!
I think for these questions, it is best to check out the less.works site. The most common course for learning more about LeSS is the "Certified LeSS Practitioner" course. The best training provider probably depends on your taste and geographical location. Hope that helps!.
After watching this video, i'm still not clear how LeSS is different from traditional Scrum. Is anyone able to explain the key differences?
How it is different from Scrum depends a lot on your Scrum Trainer (unfortunately). In short, Scrum is described, focused as one team. "Fractal Scrum," Scrum of Scrums, Scrum@Scale, and "copy-paste Scrum" means trying to copy team-scrum through the organization. LeSS tries to apply single-team Scrum with not just one-team working on the product but multiple teams working on the same Product (hence one PO and one PBL). I recommend reading more about it in the LeSS Book.
Smells like Scaled Agile with different terms. Hater: "I hate SAFe! I'll make something new and call it LeSS... with all the same things but new names." That's all this is.
Haha! Believe me, LeSS is the virtual opposite of SAFe. Neither is it new as it is around for about the same time, perhaps longer. I guess it never had enough shine, polish and roles to be the same attractive to organizations.
@@LeSSWorks It's the same with different names. Convince me otherwise. PI Planning == Sp1; LeSS does PI Retro and Demos too. It's the same thing.
@@paulstasiak8482 Uhm, no. The whole concept of PI doesn't exist in LeSS. SP1 is just for 1 Sprint (usually 2 weeks) and typically lasts about... 30 minutes. Since PI doesn't exists, so doesn't do PI Retro. "Demos" don't exists either. There is a Sprint Review but the purpose is not to "demo" things but to talk about what you are going to build next based on what the teams did the previous Sprint (usually 2 weeks)
What is with these pointless soundeffects??
It is to make the video more exciting. It clearly didn't work for you :) Thanks for that feedback!