configuration management

Within the test scene there is a vivid discussion about the necessity and use of a certification model for the test experts. The population of testers can be roughly divided into two groups: Firstly, a group that states that it will not do a better job when certified, because the current certifications like ISTQB and ISEB focus on methods and terminology, but fail to look at the practical testing skills of the tester [Bolton, 2008]. Secondly, a group who is pro certification and regards the testing industry as a young yet not fully grown profession that lacks certification models that other professions have been using for ages [Windsor 2007]. Meanwhile, voices are heard that the test profession is accepted in the IT industry and that it has actually grown into a mature profession. The website of the last EuroSTAR conference stated that a mature profession has clearly-defined standards, codes of conduct, and a number of levels of professional competence. Having all those, we might conclude that the testing profession has indeed earned its place among the IT-professions.

I've seen countless sets of requirements and RFIs come my way for acquiring new CM/ALM tools. However, it is a very rare occasion when I see a company actually publish (and send out) the project CM Plan to potential tool vendors. In my most recent encounter of this approach, the pitch was: How would you change this plan based on your CM/ALM solution for us? This project has it right—not just a set of requirements, but an actual CM Plan, and not so much, "What does your tool do?" as, "What will our CM Plan look like with your solution?"

As a piece of Christmas cheer we bring you a traditional olde English carol. It is believed that this particular carol was sung to programmers by configuration managers to earn additional money during the Christmas season. The lyrics (including mention of Mil-STD-973 and CMM among other themes) are reputed to date back to the 15th century although the author is unknown. We have been lucky enough to track down a recording of this traditional carol—click the start button.

We need to choose an SCM tool. It will mean some work to make the choice and then more work to put it into practice. At least we don’t have to worry about it from a quality perspective, though. After all, the tools we choose to employ don’t affect the quality of the software we produce. Do they? Well, let’s think about this a bit. Hmmmmmm…