views:

150

answers:

4

Working regurlarly with a small team, we try to devide the process of making a piece of software regarding each of our professions. Despite the effort to maintain a productive workflow, we tend to run into frequent issues. The most common issues are:

  • version control and keeping things controlled and organized
  • overlapping professions without needless discussions
  • lack in overview
  • communication errors

All of these issues lead to a prone to error, delayed, and declining quality project.

What are the best steps to make to prevent these issues?

A: 
  • Version control - pick a solution that you can all agree on. The group should police itself to make sure everyone actually uses it.
  • Overlapping professions - IMHO, this is a good thing.
  • Lack in overview & Communication errors - consider having (at least) daily "stand up" meetings, where everyone attends and talks about what they are doing, and what problems they have. Keep the meetings short.

If you're looking for something more formal, the last three items are addressed specifically in Agile.

Chase Seibert
Policing ourselves isn't that easy. Not everyone is willing or able to actually do that, or at least in a consistent, professional, way.Overlapping professions is indeed a good thing. I fully agree on that. But, it also inflicts discussions, which in its turn, declines productivity and quality.
Kriem
Discussions are good. By setting aside a small amount of time for them, you can make sure they don't get off track.
Chase Seibert
We seem to get off track by default.
Kriem
A: 

As for version control I would agree with Chase Seibert.

For the rest, do you have a Project Manager? It go to have someone that manages the schedules and communication so everyone else doesn't have to worry aobut it. They end up programming less, but it becomes necessary as a team grows.

Arthur Thomas
+2  A: 

Most source control providers have the ability to 'comment' particular check ins of code as you check them in. Several even have the ability to take these 'comments' and turn them into an RSS feed. I find this kind of thing useful because:

A) Everyone gets a 'high-level' view of the kinds of things people are working on, which leads to a better awareness of who's been up to what and might know why 'X'.

B) It makes people who don't comment properly stick out, and the peer pressure results in better documentation/history.

GWLlosa
Sounds interesting. How'd I tackle people who don't feel peer pressure or are just too stubborn to 'better themselves'?
Kriem
Physically. :) Realistically, those people are extremely hard to reach under most circumstances.
GWLlosa
A: 

For the "communication issues" I would suggest you attempt face to face meetings were you can, use the phone or VOIP/Skype where that's not possible, use IM then you can't talk and resort to e-mail only when you have to.

Martin Peck