Discussion panel
summary
Panel argues the original intent was to be agile (make change easy) not just deliver faster, cites Snowbird naming story and warns that managers optimize status quo so real change market is "almost zero." Recommends first principles thinking, systems design, quantitative reasoning and power-mapping instead of off‑the‑shelf frameworks. Notes hard numbers and examples: <10% do daily pair programming at an XP conference, a product owner lets Office Copilot write 10–50 emails/month, and automation and AI (co‑pilot use, even sex‑robots as a future disruptor) reshape roles.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:16Agile versus agility
- 2:23Lost meaning of Agile
- 5:36First principles in design
- 7:03Top-down vs bottom-up change
- 8:27Real organizational change
- 10:36Agile professional roles
- 13:56Agile coaching evolution
- 16:27Future of Agile professionals
- 17:55Management's role
- 19:59Organizations' true purpose
- 25:12Larman's laws on behavior
- 27:40Q&A: AI and human interaction
- 31:13Q&A: AI and intuition
- 33:25Q&A: AI as product customers
- 36:37Adapting to disruption
- 39:31Q&A: AI as Scrum Master
- 42:00State of teamwork
- 46:17Final advice
related talks
46mDiscussion panel
01h 33mPanel - Predictability and Productivity...Does Agile Help?
41mPanel discussion: Agile in the modern age
36mFrom Software to Systems: Modern Agility
38mPolyglot Agile
45mAgility in non software teams, lessons from the front lines
04mInterview with
55mDiscussion panel - The Future of Agile