A change lead by the team instead of the leader
Thanks for sharing these thoughts, Aleix! I really like the idea of setting a vision and letting the teams decide how to catch up with that vision. Any insights around how to go about teams that are more resistant to complying with that vision?
I reckon that not every developer is open to trying TDD, pair programming, trunk-based development, etc, but yet those are practices that add value, I was wondering what was your experience convincing the more resistant people to go in the direction that you find ideal or if in the end they convinced you to change your mind.