A race track is built to accommodate a certain class of race car. It provides a path in which a race car can travel around to start and finish a race. The track is built as a permanent facility designed with materials and formation to ensure the track is easily maintainable and to enable that class of race car to travel in a reliable manner. It is also important to build the track in a way that allows the race cars to reach their peak performance.
What does this have to do with configuration management (CM)? The race track is a lot like a CM infrastructure needed by product team to support the building of product. The race car is a lot like the CM tasks that are executed to help the project race to the release finish line.
CM Race Track at the Product Level: Deployment
CM at the product level is the infrastructure race track that must be built to support lean and efficient engineering for the project. When establishing CM infrastructure, it is recommended to have a separate CM effort that is independent from the engineering project whose goal is to use the CM infrastructure to create a set of deliverables known as a project release. Another goal is to complete the CM infrastructure in time for the engineering project to use (servers, tools, code repository, build processes, training, etc).
It is advisable for the product owner to provide the CM professional(s) with lead time to build an appropriate CM infrastructure for the product so that when project work starts, a functional set of CM procedures and technology are available to control that work and get it down the race track with speed and reliability.
We can think of CM at the product level as a focus on building and deploying the CM race track infrastructure for maintainability, reliability, and performance. CM, at this level,