6:30p.m. to 7:00p.m. - Networking
7:00p.m. - 8:30 p.m. - Feature Presentation
8:30p.m. - 9:00p.m. - Question & Answer
As the co-creator of LeSS (with my friend and colleague Bas Vodde), after a decade of working worldwide with large product groups in their adoption of LeSS (Large-Scale Scrum)(https://less.works/), organizations are starting to realize that the main goal of LeSS is not to enable traditional big groups to "meet their commitment" more efficiently. And they are realizing that LeSS is not “Scrum contained within each team, with something different on top.” It seems some scaling frameworks contain Scrum like a fire fighter contains a brushfire.
Then what is LeSS about? It is to see the ineffectiveness of traditional large-scale organizational design and to change it, by descaling with LeSS towards a simple model for multiple teams that optimizes for agility (flexibility), learning, and flow of value. It is figuring out how, with multiple teams, to apply the simple principles and elements of Scrum that encourage empirical process control, transparency, self-managing teams, and systems optimization.
But any structural change per definition challenges the status quo of middle-management and single-specialist positions, leading to the dynamics of Larman's Laws of Organizational Behavior.