Team communication - Make sure there is a way for all developers to brainstorm easily, we did this by setting up an IRC channel. But it needs to be used obvious

Team communication - Make sure there is a way for all developers to brainstorm easily, we did this by setting up an IRC channel. But it needs to be used obviously, which is the hard part. Give credit - If any one even mentions an idea in passing, etc and it is later discussed, that mention should be attributed. 'A few weeks ago Mike suggested RabbitMQ, we did some research and we've decided this is the best solution'. Of course for obvious good work praise should be given. Celebrate team effort - There is a problem in production, your developers are working hard to pinpoint. Once the dust settles and you are sending out your final status email, be sure to praise the team effort, include names (be sure to include anyone that even had the slightest impact, seeing their names together reinforces the team) Other obvious ones - sufficient funds for tools, hardware, training, books etc. code reviews, personal growth plans, frequent employee performance reviews (6mo). motivation is tough, sometimes people need a little peer pressure. Give an unmotivated developer a visible high priority, small(!!), project. Something you know is a homerun. Email the stake holders and CC the developer explaining the developer is on it and it's their #1 priority. Give them plenty of time, but just knowing that people are depending on their work helps some people with motivation.