Video

This video is way underrated given it´s content longterm impact

Great class, Professor Craig, good to know that we are on the AI wave...

I found some of the answers to these questions mixed. The host let Craig and Bas off a little, when they didn’t engage with some questions. It’s not that they didn’t answer them when they should have, it’s that we don’t know why they didn’t answer them.

Promo-SM

Hardly any views...? Is Germany not interested in scrum/Less/efficiency?

Management innovation IS a crowded place. Too bad it is crowded with consultants not managers

Great video, I look forward to learning the LeSS organizational design framework from study and empirical learning. Exciting.

This is a great presentation, thanks for making it available

Splitting a product into multiple repositories can be an effective strategy to improve design. Many programmers are not good at designing or test-driving. They might not understand the purpose of the design or architecture. Splitting a product into multiple repositories makes it easier for programmers to keep the code cohesive.

Great stuff

Master class, thanks for sharing!

😢 Promo'SM

What's the difference between less and scrum of scrums.

Fingers crossed for Less and its practitioners all over the world! IT needs you! 😎

Great content! I'd wish more people in the Agile space are aware of this stuff.

It seems to me that accidental specialization, if done at the component level, starts sounding a lot like ownership, which I think is what LeSS authors are trying to avoid.

Loved this talk, the point about writing code incrementally and the challenges developers face makes a lot of sense.

How would this work on a platform area that doesn’t have products or customer interaction? Think people that work on infrastructure , network, for the entire company (not one product or another) etc

Great video Craig!

was it : Sidney Dekker (not Decker) .. what gets measured, gets manipulated

Nice talk. Expecially when you say "dependencies are opportunities, not interrupt". Great. And Lego part, too.. :)

Fantastic talk!

Good stuff!

Principles as discussed are great! But what really should be considered is to let go of the misguided ambition to scale. Chop up your big product in a suite of very loosely couples Apps.

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.

No separate BL means what? No separate teams neither? How does that work for a complex product with specific skills and technical challenges per module? Do you have one or several technical leads/scrum masters if there's only one BL? How about the Product Owner? Only one for the entire product? What if it is about tens and tens of features and modules? The product owner only does "the vision" but does not interact with customers?? This seems quite disconnected from many real life examples.

Tks!

Best agile/less trainer i had pleasure to work with.

Thank you Craig - found this from Tom's post on LinkedIn. On sources of clear causal influence, potentially an element under system modelling, it's worth noting when where there is no strong/reliable causal influence. E.g. thorough estimation does not guarantee ... Started wondering why the world accepts sharing of knowledge without proof as it seems to be a well-known and commonly accepted situation?

Great stuff Craig. There are several things I'd like to discuss such as the difference between quantification as a reasoning tool (no measurement), and levels of causes. But amazing job in 45 minutes. I'll recommend it on Linkedin.

Great video and explanation. Thank you!

Concepts pretty easy to follow. Thank you

This talk changed my world view. Since I saw it I started to dig into the reliability of various study results, statistical math, Bayes' theorem and all the things you CANT'T know from studies due to the limited information available from the data. Understanding that so much (almost everything) of what is taken as fact from observational, underpowered, biased and p-hacked studies is actually unproven claim is ground shattering. And of essential consequence for political/social/economical/psychological (ans also agile, unfortunately) arguing based on those study results. Thank you, Craig.

can you discuss the differences between LeSS and SAFe?

thanks guys! a great talk

I like how this points to an actionable path towards so called psychological safety. That is: Pair-programming provides practice in communication and social skill. And more over, it does so as a practice inside and towards the value we want to bring to our customers. Purposeful.

Ankommen und checkout insgesamt etwa 45 min? - im Vergleich zu 75 min. Fach-Themen/ Arbeiten? Habt ihr beispielsweise ein Feedback Board, bei dem Teilnehmer jederzeit Feedback abgeben können…?

Greg. Thank you as always great insight.

Very insightful! Now I understand better what makes Scrum Masters who understand engineering practices more effective.

very good explanation about product owner. thanks

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.

Nice one, with an amazing visualization!

I work for a client where LESS is attempted with multiple vendors working with component teams instead of feature teams. The main reason is essentially what you guys say - lack of trust from client towards the vendors as each vendors performance is measured by a set of KPIs in regards to defects, SLAs etc with monetary penalties etc. This then leads to vendors wanting to have clear control over the code they have responsibility for to be able to control the KPIs their performance is measured by. Thus not agreeing to work shared on code (unless with PR) to the code they each own. And also not necessarily wanting to do PRs as each feature has to be delivered as a fixed price due to contracts with the client and not knowing if the PR will be accepted by the other vendor etc. Overall this is rooted in my understanding in a deep seated decarde long established client culture that is very much used to steering and controlling vendors with a clear hierarchical difference between client and vendors. Any ideas how to proceed here?

Great video,keep it up!🌏🏠🏡🏪

I don't understand this. He just talks a lot without saying much

Thank you guys. I am quite having fun watching these sessions, and on top of it, learning some stuffs.

After watching this video, i'm still not clear how LeSS is different from traditional Scrum. Is anyone able to explain the key differences?

That was great fun, thanks a lot for this session. To all: Find me anywhere in the internet as docXmaier.

Bravo Magnus! 👍🏼

great to see you on CZcams, Craig - not as good as in person, of course! Thanks for all of the good ideas that you share with me and so many others.