I'll share my experiences in creating a low-risk, long-running, low-commitment, high-safety environment for people to learn, and above all exercise, good software development practices.
It’s an issue that crops up again and again: People acknowledge that something is a good practice, but they still don't do it (the inverse of the "Copy and Paste Effect"). In my case, it was Test Driven Development (TDD)...and it was so confounding that I began asking (and trying to answer) two questions:
1. Really, why not?
2. How can I convince, teach, and support people to start?
While asking and answering these questions, a format emerged that takes advantage of Mob/Ensemble Programming to ensure a common understanding among participants.
This format (dubbed "Quality Dojo") has, through continuous assessment and improvement, worked incredibly well for us. I'd like to share with you our experiences in creating and improving a low-risk, long-running, low-commitment, high-safety environment for people to learn, and above all exercise, TDD. It's a sure bet that the lessons we've learned the hard way will be helpful for you in teaching and encouraging good development practices in your teams.