| I am working in a team where code review are mandatory, but this was not so hard to implement because they are part of regulatory requirements. Your culture change is a problem of change management[0] There are different model, but some example of actions, are : * finding a sponsor * creating a common vision of the end result and benefits, communicate it * identify early adopters to deploy it with them * identify people resistant to change (and why ? Is there a way to convince them ? [1]) * communicate your early success Most of it is basically common sense, but it is good to have a kind of check list to help you establish your plan. One thing that is important, because it is otherwise frustrating, you have to lay out very clearly what are the "coding rules" and what the code reviewer will actually check up front. If the "contract" is clear, it is easier to follow it. The most annoying situation is written a whole bunch of code and having to rewrite everything. [0] https://en.wikipedia.org/wiki/Change_management [1] for example, a human tendency is to resist change because a fear of loss of power. So using that you could decide that the guy that is more resistant to change will actually be the one responsible for doing a fair share of code review. |