Keynote (Ericsson) - Scaling Agile with Large-Scale Scrum - Craig Larman

Keynote (Ericsson) - Scaling Agile with Large-Scale Scrum - Craig Larman

[@kajbeuter9139]

KZbin algorithm brought me here. But now I have several pages with notes and graphs I've taken while watching that lecture. Inspiring. Thank you! It will definitely enrich my future agile trainings.

[@peolchowik]

2:05 End of bad joke :) and beginning of speech 5:13 SAGE project and “3 don’ts of scaling” ("find 10 best people and do it themselves") 6:36 thinking mistake - IT does not make donuts 9:40 Roots of Scrum - “New new product development game” 11:32 Why was it called “Scrum”? Move the ball down the field 12:24 What's written on your business card? Flow of work through the system 15:48 Organization before Scrum adoption. Who is Scrum for? 18:24 "How long does it take" story 21:00 "Contract game" story (internal contracts) - I prefer the newer version of the same story, in other recent Craig's clips 30:58 Two parties competitive game - internal conflict & competition 31:50 "We are near the end - 6 weeks before go-live" - management by magic words 35:50 What’s inside R&D tool box? How does the system get weaker 37:40 Scrum is trying to address root causes of "contract game" 39:00 In Agile there is no R&D contract 40:08 Role of Product Owner that „gets the steering wheel” - Scrum is not a “change for the R&D” 43:37 The end of business ordering from the menu - we go to kitchen together 44:09 Self-organizing teams of Scrum 44:55 “Potentially shippable” - not every sprint must be an MVP 47:02 Business Agility - MVP becomes flexible 48:01 Definition of Done - what needs to be potentially shippable 49:49 De-scoping - Scrum reveals variability that exists systemically in IT, it’s better to do it early 50:37 Definition of Un-done - evolve over time - journey of improvement 53:17 Release sprint - how to handle un-done work? By the team or by pairing the team with “un-done team” and “the rule of 3” 58:07 “resource mentality” and variability in productivity 1:01:40 Component vs Feature teams story - more recent presentations of this idea by Craig are better, imho 1:06:00 LeSS framework 1 & 2 - high level description of framework 1… 1:11:04 …and framework 2 - requirement areas by “looking at the customer” and not the type of work 1:14:45 Communities of Practice 1:18:00 Multisite vs dispersed team 1:22:55 Good bye bad joke :-)