From code to software, a team journey
summary
Examines how role-based silos (developers ignoring methodology, QA ignoring architecture, Scrum Masters detached) undermine shared responsibility and XP principles. Argues for multidisciplinary teams, leadership that supports collective ownership, and rethinking what it means to be a software developer to restore cross-functional collaboration.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 6:05Three skill domains
- 12:04Technical silos
- 16:43Organizational silos
- 21:05Breaking silos
- 27:29Team alignment practices
- 31:17Q&A
related talks
49mExtreme Professionalism - Software Craftsmanship.
46mArchitecture for Cross-Functional Teams
52mFrom Code to Complexity: Shifting to Systems Thinking in Software Development
45mTeam and Software: Making an Impact as an Architect
47mUnlock your autonomy. Improve your software design
53mSoftware Design: Beyond Boxes & Lines
59mDo You Know Da Wae
01mFor the Love of Software