How Lean is your Scrum
summary
Shows concrete fixes a remote Scrum team at Red Hat actually applies: add Kanban-style WIP limits, pull from right to speed flow, treat maintenance/bugs as first-class backlog items, push automation and CI/CD earlier, and run shorter meetings with agendas and calendar padding. Backed by numbers the talk cites: ~80% market share for Scrum, Lean adoption stuck at 10% success rate, and risky team mixes like 5:1 engineer-to-QA that block flow. Examples include social “coffee” slots, calendar 25/50-minute meeting defaults, and measurable reductions in meeting fatigue and handoff delays.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:13Motivator Remote Scrum Challenges
- 3:45Motivator Scrum is evolving
- 7:12Waste Defects through a Scrum Lens
- 11:34Transportation
- 14:55Motion through a Scrum Lens
- 27:28Lean Tools and Approaches you can apply
related talks
44mHow Lean is Your Scrum
40mHeavyweight agile methods?!? Let’s make them Lean(er).
39mScrum at Scale
35mMy journey from misshapen Scrum to reliable Kanban
43mEver Since We Started Doing SCRUM Everything's Great. Not!
01h 04mIs Agile Still the Answer? Lessons from Real World Agility
15mAdvanced Scrum techniques for optimal delivery
01h 27mPNSQC 2014 - Halim Dunsky