3 Beliefs You Need to Let Go to Start Your Agile Journey
summary
Three core beliefs get named and overturned with concrete practice evidence: batching work is most efficient fails in a multitask simulation where five customers and one developer show huge lead‑time increases versus single‑piece flow; specialists beat cross‑functional teams breaks down in a hands‑on 18‑minute tower exercise that forces role switching and exposes decision bottlenecks; formal org charts solve coordination collapses after running iterative 5‑cycle process experiments and short retrospectives. Games built for learning actually surface misconceptions and paired reflection makes new practices stick.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:233 layers of culture
- 7:47New processes can be rolled out to organizations and teams
- 8:02Changes in an organization chart will lead to similar changes in reality
- 9:56Reflection together
- 11:37Marshmallow Challenge
- 12:41Multitasking Name Game
- 16:41Assumptions and beliefs hold us back
related talks
24m5 Lessons Learned During Agile Transformations
55mOnce Upon a Time in Agile
34mLeadership Lessons from the Agile Manifesto
33mWhy You Should Not Start an Agile Transformation
49mAgile is a Dirty Word
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
34mAgile-battle
05mAgile: "I have never" Game