Tuesday, February 23, 2010

Programmer - How do you communicate effectively in a small development team?

Programmer Question

I work in a small team (4-5 developers) on a single project. Every member of our team is developing a different functionality from our project and their are highly independent. In fact, some members use technologies that other member doesn't know about. It's still a single project and there a lot of common business logic in it.



In addition, most of the members are completely unaware what and how the others are doing. Somehow, we manage to avoid code replication (credits for our team-leader, but even he is not completely aware what is happening). I wonder, what is a good practice to keep the whole team on the track what is going on. For example if some one from the team quits or is missing when an important fix should be maid - it's difficult for the others to handle.



We have a policy, for conducting code-reviews, but only the team-leaders and one member of the team participates in it. The other "regular" members do not take part, there.



Also, we have a "newslist" for checkin-s committed in the source control by our members, but this seems too boring to deal with and it looks like nobody is taking time to read what others have just committed (and it's not effective, to be fair).



So, I wonder what is a good practice in this matter. What experience do you have? Is there a solution at all ?



Best Regards!

No comments:

Post a Comment

LinkWithin

Related Posts with Thumbnails