configuration management

Many people know that peer reviews can help them to produce better-quality products, but most organizations do not use this potent tool. Why? Because, although they would like to experience the quality benefits, they can't justify the costs they would incur.

Our test teams often struggle for so long ... to do so much ... with so little, and they usually manage to just squeak by. In the next cycle when asked to do even more with even less, they are likely to fail. Working harder and smarter isn't enough-the rules of the game must change. Innovation is the currency of success. Using his experiences from several years of success (and a few months of failure) in driving innovation, Heath Newburn will show you how-through innovation-you can drastically increase your team's value and your contributions to your organization. Uncover the secrets to managing change and learn: how to systematically create innovation and foster creativity, how to generate ideas and use your whole team to identify and build on the best of those ideas, how to implement a plan for success, and how to overcome the inevitable obstacles with the six secrets "they" don't want you to know.

Why do version control? I remember the first time I learned about version control. It was for a SunOS based project, and my manager told me to learn SCCS, and put all of our sources in it. Its been years since I've used SCCS, and I am not always sure if it had features I also remember in RCS and PVCS. They are all similar tools. Since those younger years, I've learned that version control is much more than a glorified file repository, and has more to do with people working toghether, collaborating on their project code base.

Many in the software engineering world consider build, package, and deploy the core areas of configuration management (CM). To highlight this, many CM jobs are titled “build engineer” or “release engineer” with responsibilities that focus on the tasks of building, packaging, and deploying releases.