My company is now trying to employ a major shift in our working process. One of the new roles that were introduced in this process is "The person who makes sure that no double-coding takes place among separate projects"(We couldn’t come up with a better name...). I'm not really sure what's the person's job called, but I'm guessing it's called "Software Configuration Manager". And I got that job, among other stuff.
We have several projects that use one major product (an engine written in C++) and each project customizes it to their own needs. Now, a problem has been gradually growing in the past several months - Projects were basically writing the same code twice for a lot of tasks. Instead of spreading the wheel, they re-invented it each time.
So now, I have to learn a whole new area. I need to start coordinating the different projects in my company, making sure no one re-invents anything, and basically be the "know-it dude". My job would be organize status meetings for common project problems, bother the project managers about running tasks, and basically be pain in everyone's neck. I'm not sure I'm going to like doing this, but I can tell one thing for sure – for the next couple of weeks I'm going to be learning a lot – Which I always enjoy doing J
I was thinking that I could really use a book about software configuration. Specifically, I was checking out this book: Software Configuration Management Patterns: Effective Teamwork, Practical Integration . It seems to cover mostly stuff related to build management, though. The basic premise is that I will be dealing only with the 'features', not their implementation. Do you know this book? Can anyone offer up a better book, or another resource for learning best practices when it comes to this subject? Is this really what I need to learn?