"To water for 300 years"
summary
Maxim Yefimov describes why large-scale rapid technological transformation in a bank fails: he discusses limits of changing people’s mindsets and change acceptance, and why creating a fast CI/CD pipeline (lead time one hour) is useless without changing teams’ production processes. The talk names concrete focuses—supporting teams with engineering practices and product-relevant changes, maintaining an information ecosystem around transformation, using continuous feedback rather than one-size-fits-all recipes, and setting an ambitious target (e.g., ‘elite performer’ status) even if nearly unreachable.
AI-written summary · about
chapters (5)
related talks
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
23mIts transformation! But, is it though?
34mDiscussion Panel
01h 02mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
54mEffecting Change—The Art Of Leading Teams
43mSoftware Eats Culture For Breakfast
47mContinuous Deprovement will eat your product for breakfast
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas