in reply to Re: Tracking code changes
in thread Tracking code changes

The most important part about version control within a team structure is communication.

You hit the nail on the head there! Previous job there were only 5 of us in the whole IT deptarment. I could yell down the hall or at my office mate and proceed. This current job, the IT dept has more people in it than my former employer had total.

It's mass chaos. Most of the worker bees don't read the team leader meeting minutes and therefore miss important info and end up doing something stupid. Of course important things get left out of the minutes which is another disaster. I also won't go into the whole issue of some of the team leaders seem to forget everything said in the meetings too and direct their workers based on false assumptions.

We have a mess and I'm thinking version control is the first step forcing better communication. If we can start tracking the stupidity eventually we can start holding people responsible and get them to fix their problem. I'm thinking we've got at least 10 years before things will be running close to smoothly.

Replies are listed 'Best First'.
Re^3: Tracking code changes
by chromatic (Archbishop) on Aug 23, 2006 at 17:55 UTC
    We have a mess and I'm thinking version control is the first step forcing better communication.

    That's a bit backwards. Version control is a tool. Without better communication, you'll end up with a tool that some people use, some people don't, and a different kind of mess.