interesting likes to dislikes ratio... guess there were too many sales-related topics in first 20 minutes. timestamps might be useful. 4:35 start of Craigs keynote 6:05 actual start - SAGE project fail 7:05 descale the organization - 3 don't's - you are not digging the ditch 13:55 reducing suffering in product development 14:24 some photos of LeSS 19:00 elements of LeSS 22:15 LeSS books and other sales-related stuff 27:35 feature and component teams story 33:22 special-special people that think that they don't need to join the Scrum team 36:02 how long does the transition take? 1 hour 39:07 how to organize the self-organizing team? don't do it, let them self-organize 41:43 job safety, but not role safety 45:39 how many managers do you need - all management is waste 47:45 analogy of hospital employee - heart surgeon 51:49 why transformation changes fail - Larman laws 54:50 who does PM's tasks in Scrum Team? 57:07 grow from within fun part :-) 1:00:45 component teams and their impact on your development process 1:03:40 feature 1 - how will things play out? 1:04:43 - how to understand it? 1:06:43 - who decides what components are touched? 1:10:00 - who breaks down the work? 1:11:40 - code integration - it doesn't happen in synchronization 1:13:33 - who will integrate it? 1:13:55 - who will test it? 1:14:20 - who takes care of the big picture? it get's better: 1:16:33 what happens if one of the component teams has nothing to do? local optimization 1:19:13 what happens after the release? staff up! 1:22:40 what will not-busy people do? pump out code! 1:24:15 what happens after another release? 1:25:27 at lease we get a high quality code... nope! 1:29:26 lean waste of not utilizing full potential of a person
Fascinating conference. Really disruptive. Not like 90% of the things I have seen about scaling scrum. And I think you got a point there. Especially about breaking component teams. Food for thought. I agree that decision to do it can be quick. But implementing it can be more difficult, especially at the beginning. However on mid term or long term, I believe it can bring fantastic results I you can have cross functional teams with people skilled on multiple components, capable of delivering a feature end to end. The speed of delivery could increase dramatically. Thanks for those clear ideas.
Who could please point me to the meta analysis that Craig mentioned at around 8:04 about programmers productivity? I don't understand the name correctly, so I could not find this.
Does anyone know which other video is recommended to be viewed after this one? It seems to that this was only an intro; not much elaboration on LeSS framework, concept by concept.
+K. Ramesh Babu The website has a very nice documentation. See less.works/less/framework/introduction.html and note the table of contents on the left. It helped me a lot. The home page also has a picture linked to the same articles.
interesting likes to dislikes ratio... guess there were too many sales-related topics in first 20 minutes. timestamps might be useful.
4:35 start of Craigs keynote
6:05 actual start - SAGE project fail
7:05 descale the organization - 3 don't's - you are not digging the ditch
13:55 reducing suffering in product development
14:24 some photos of LeSS
19:00 elements of LeSS
22:15 LeSS books and other sales-related stuff
27:35 feature and component teams story
33:22 special-special people that think that they don't need to join the Scrum team
36:02 how long does the transition take? 1 hour
39:07 how to organize the self-organizing team? don't do it, let them self-organize
41:43 job safety, but not role safety
45:39 how many managers do you need - all management is waste
47:45 analogy of hospital employee - heart surgeon
51:49 why transformation changes fail - Larman laws
54:50 who does PM's tasks in Scrum Team?
57:07 grow from within
fun part :-)
1:00:45 component teams and their impact on your development process
1:03:40 feature 1 - how will things play out?
1:04:43 - how to understand it?
1:06:43 - who decides what components are touched?
1:10:00 - who breaks down the work?
1:11:40 - code integration - it doesn't happen in synchronization
1:13:33 - who will integrate it?
1:13:55 - who will test it?
1:14:20 - who takes care of the big picture?
it get's better:
1:16:33 what happens if one of the component teams has nothing to do? local optimization
1:19:13 what happens after the release? staff up!
1:22:40 what will not-busy people do? pump out code!
1:24:15 what happens after another release?
1:25:27 at lease we get a high quality code... nope!
1:29:26 lean waste of not utilizing full potential of a person
You, fine sir, are the real mvp!
Don't be fooled by the almost non-existing sound in the beginning, it gets better with the main speaker.
yes i did had a thought whether this is a good one. after 3 min it was better
1.5x playback speed is recommended
Fascinating conference. Really disruptive. Not like 90% of the things I have seen about scaling scrum. And I think you got a point there. Especially about breaking component teams. Food for thought. I agree that decision to do it can be quick. But implementing it can be more difficult, especially at the beginning. However on mid term or long term, I believe it can bring fantastic results I you can have cross functional teams with people skilled on multiple components, capable of delivering a feature end to end. The speed of delivery could increase dramatically. Thanks for those clear ideas.
Very interested in LeSS but what was that picture slide show at the beginning? Weird..
Craig Larman先生可以说是我的启蒙老师，至今仍然影响着我，所以要在这里向您表示感谢。他的对象思想，过程思想对我的影响是深远的。Thank you very very much. I read your book twice a year.
Who could please point me to the meta analysis that Craig mentioned at around 8:04 about programmers productivity? I don't understand the name correctly, so I could not find this.
Have you found the study? I do not get the name right either. A response would be very much appreciated.
@@andymoesch no, nothing yet
@@robertg.7407 Thank you anyway for your response.
Does anyone know which other video is recommended to be viewed after this one? It seems to that this was only an intro; not much elaboration on LeSS framework, concept by concept.
+K. Ramesh Babu The website has a very nice documentation. See less.works/less/framework/introduction.html and note the table of contents on the left. It helped me a lot. The home page also has a picture linked to the same articles.
from his book.
His discussion of component teams is dead on. Here's the time link: ua-cam.com/video/phOCA3myNws/v-deo.html
I watched this video. can i specify this for SEU?. its a very good one.
Thanks Craig
Hi Albert.. thanks for your comment.. yes you can earn SEUs by watching our videos :)
which category ?
Category E: Independent Learning.
Though I asked, I did not used this SEU since i already had about 200 in various category