Reduce Small-Team Culture Shock with Agile
summary
Describes why hires from traditional IT bring survival strategies like reflexive change resistance and intentional deinvestment, with concrete examples (125 independent services, 250 server instances) showing fragmented ownership and toxic microaggressions. Lists observed behaviors: compartmentalization, bonding through negativity, repeated reimaging, and flat “no” responses in sprint meetings. Recommends specific fixes: involve ops early, pair ops with a developer for big infra changes, redirect negativity into actionable feedback, and fire or retrain people who persistently sabotage team safety.
AI-written summary · about
chapters (6)
- 0:00Traditional IT culture shock
- 10:39Coping mechanisms in IT
- 13:57Impact of toxic culture
- 17:42Transitioning to agile teams
- 20:41Managing digital migrants
- 26:42Psychological safety conclusion
related talks
59mDelivering Agile Methodologies & Emerging Tech in Hostile...
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
32mTales from the DevOps Transformation Trenches
43mSoftware Eats Culture For Breakfast
32mSolving the Dev/IT Cultural Divide with Operational Agile
19mDevOps transformation tailored to organizational culture
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
38mConway's law in practice: Agile teams & Microservises