How do you motivate your team colleagues to learn, use and apply best practices? [duplicate]

Question

Possible Duplicate:
How do you motivate peers to become better developers?

How do you promote and how do you assure that in your new project best practices like unit testing, TDD, separation of concerns, SOLID principles and others are applied and used?

I’m trying to get there by setting a high target for the unit testing code coverage. I am thinking that to be able to properly test your code you are forced to do a better code design. However, this is going not going too well. After a few months we have projects with low code coverage and bad, ugly code.

I have the impression that the benefits of best practices mentioned above are not well understood and embraced by the team.

Your ideas on how to go to higher quality?

Answer 1

Sounds like you have two issues: poor test coverage and poor coding conventions. Solving one does not solve the other. I'd recommend you approach each issue separately.

People are natural skeptics and may need to be convinced that these are areas that they need to improve. Identify their objections. Once you know why they object (e.g., lack of time, cost of maintenance, etc...), you can tailor your response to ease their concerns.

If there are no objections, you may need to explain the benefits as they relate to all the stakeholders (not just the developers).

If all else fails, then lead by example.

Answer 2

Have you considered code review. And include reviewing the test code as part of it. Code does not get pushed to prod until the code reviewer is happy.

Answer 3

The most effective way of getting people to adopt best practices is to make it easier to use them than not. A prime example was in one company who implemented a series of Word Perfect macros to aid the production of (non-programming) documentation. There was no compulsion to use these macros, but using them did make such documentation easier than straightforward formatting and typing. They were very widely adopted and improved the standards massively and quickly. Given that you are describing poor test coverage, and poor coding conventions, it might be appropriate to set up minimal code testing skeletons, with always fail tests in the skeleton by generation from the requirements, or from the code itself. Equally for the coding conventions, a "pretty printer" formatting routine called when code is compiled; or warnings from a cross reference listing, again as part of the routine for generating code might help.

I would emphasise that I do am not suggesting anything extensive, comprehensive or complicated - a very simple utility introduced will have have some effect, and multiple small utilities will be synergistic - the whole will be greater than the sum of the parts.

Answer 4

Personal interest is a key factor in making almost everybody get active. This is something I had experienced and it's so effective. It's not a theory, but maybe a managerial approach to involve the team in the benefit (or even lose) of the project. If you know that by selling the product, 1% of the total revenue would be yours (a team of 10 will make 10%), then you're more likely to work better and with higher quality, since you now have something to gain. This interest doesn't necessarily should be monetary. For example, an employee may work better, just because he expects to be presented as the best employee of the year at the yearly first of a corporation.

In other words, IMHO and as a suggestion, I think developers should get a feeling that they don't just work and are paid their salaries. Rather they should think that they will gain something subjectively valuable. :)