Revealing Mechanisms to Create Resilient Teams and the Organizational Culture That Supports Them
summary
IIJ Nagoya Tech Section 4 describes running agile for 4.5 years as a vendor to make teams resilient to business, technology, and people changes by creating recurring rituals and practices. Concrete measures include weekly 180-minute LT sessions (700+ topics), a weekly Scrum Master guild, coaching, mandatory camera-on collaboration, pair/mob programming, 2–3 day onboarding bootcamps, and forming all-in cross-functional teams that own frontend, backend, infra and ops; they emphasize small sustained practices over static handbooks and treat the organization as a product.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:12Vendor teams background
- 7:26Why mechanisms are needed
- 8:51Work mechanisms overview
- 11:22Lightning talks and culture
- 12:25Scrum master gatherings
- 13:48Partner health checks
- 14:10Coaching approach
- 14:52Team building practices
- 16:36Online communication standards
- 17:21Cross-functional teams
- 18:05Failed attempts and lessons
- 19:07Team outcomes and summary
related talks
43mResilience, Scalability, Performance – On the Architecture of Agile Product Teams
34mNative Agile Psychology of Teams and Individuals
22mHow to create agile teams and foster the culture of excellence while developing games
35mBuilding and Growing an Agile Team
38mPolyglot Agile
53mTips & Tricks to Become a High-Performance Team
47mAgile experience in changing environments and the challenges faced
15mThe agile leadership mindset: Embracing continuous change as a leader