Processes & Tools over Individuals & Interactions
summary
Claim: values and principles matter more than imposing frameworks; evidence: one team spends a 5-hour planning meeting because backlog lacks priorities, another deliberately split weekly sync into two 30-minute meetings as an experiment, measures impact for one month and reverted after one month when it worsens flow. Expect about ~7–8 hours of ceremonies per two-week sprint (roughly 10% of time) and focus on small experiments, visible problems, and reverting changes that don’t help.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:26Typical Mistakes
- 4:54Complaints about Scrum
- 11:20How to be Agile
- 11:47Scrum
- 13:13Paavo
related talks
16mSmall Scale Scrumming
46mFacilitation Foundations: Eliminating Waste From Agile Meetings
46mWeeks of coding can save you hours of planning
11mLeading Agile Teams to Success: Lessons from the Trenches
01h 00mMob Programming, A Whole Team Approach
34mBuilding a Culture For Developer Productivity
59mSet Your Teams Up for Improved and Enduring Velocity
16mLightning Talks