Keep an environment where developers, and all employees for that matter are allowed to make mistakes.  If people are afraid of repurcussions, then they will spend more time trying to hide or make excuses for an issue rather than fixing that issue.  If something is going drastically wrong on our website, I much rather we all dive in and get our hands dirty fixing the issue than figuring out who was responsible for the problem.  When the dust settles, you can have a post-mortem to discuss what went wrong and how to avoid these issues inthe future.  These meetings should be informal, and informative, not a forum to place blame.  If you have good developers who take pride in their work, they will take ownership of their mistakes and learn from them.  You might even find the problem was caused by something entirely different than originally thought.

Related posts:

1. good development teams share information Sometimes its hard to effectively share everything among all members...
2. deployment schedules are not effective Simply put, deploying code on a set schedule is not...
3. How to Effectively Use the Development Community This may seem obvious to most, especially to regular blog...
4. Use Project Collaboration Software We use BaseCamp here for managing projects. It is extremely...
5. Web Development: Because We Care As a web developer you make a product (the website...

Related posts brought to you by Yet Another Related Posts Plugin.

Filed under:
dev team, experiences by bill breen