Panel discussion: Agile in the modern age
summary
Panelists argue that modern leaders must understand software architecture and align organization structure to it, treat failures as learnable (business vs software “fail” distinction), and arrange vendors by compatible principles rather than mixing opposites. Teams use concrete practices: enforced early co‑location (example given: 16 months co‑location before full remote), strict rituals (daily standups, retros, monthly shared meals) and a centralized artifact hub like a single war board (Miro/Mural/Figma links) to keep information flowing.
AI-written summary · about
chapters (6)
- 0:00Introduction and icebreaker
- 2:37Panel introduction
- 7:01Modern leadership challenges
- 14:32Multi-vendor collaboration
- 25:32Remote work adaptation
- 35:12Q&A session
related talks
49mAgile and Architecture: a meeting of the undead
47mAgile and Architecture: a meeting of the undead
08msoftware architecture and agile development
50mDiscussion panel
36mFrom Software to Systems: Modern Agility
38mPolyglot Agile
55mDiscussion panel - The Future of Agile
41mCultivating Architecture in an Agile World
