Posts Tagged
‘configuration management’

“Scaffolding” is a term often used in education, but in our experience, rarely followed to a significant extent. Scaffolding allows us to grow a student in capability by starting easily and providing progressively more intricate and involved exercises. This approach actualizes Lev Vygotsky’s concept of the zone of proximal development. When training clients, we must […]

We have seen the word “layoff” used during a reduction in force. A reduction in force is a mass firing, often engendered by management ineptitude but sometimes driven by market forces. A layoff occurs when we temporarily dismiss an employee, but we provide preferential treatment for them when the market bounces back. Even with the […]

There are a number of quality tools that can help to evoke the risks that may be associated with your project. One such tool usually associated with cause and effect is the Ishikawa diagram. We can use this tool to explore risks as well. We will explore what happens (cause) and how it will impact […]

We can use value analysis and value engineering techniques to improve our product cost structure and ultimately our value proposition.  The analysis phase of this activity is called value analysis. The design phase of this activity is called value engineering.  We are a bit constrained during these activities since as we have a product already […]

We would like to thank those that have sent us some ideas. To sweeten the pot, we make the offer below. We have decided to extend our story acquisition for the configuration management book.  Please send your stories and techniques to my email address at Jon.Quigley@valuetransform.com Elaborate all that you can (2-15 pages) without divulging […]

We received some questions about how configuration management and change management work together. Configuration management is a component of the change management process. The business requirements or demands drive the scope, which is a project management function (requirements elicitation and control of scope). On completion of the elicitation, we have the scope baseline for the […]

Another piece of the configuration management pie is the ability to move backward and forward from revision to revision. To demonstrate the importance of this concept I will relate a story. There once was a developer who was writing in assembly language for a new product.  He was incrementally developing the features for the product […]

Configuration auditing occurs so we can verify that what we said we were going to do actually happened. MIL-STD-973 specifies two flavors of auditing: functional and physical. Functional configuration auditing occurs when we verify that the change functions as the engineering change proposal specified it would. A change can be to hardware, software, or both […]

Configuration control is generally, what first comes to mind when somebody brings up the topic of configuration management (CM). While it lies at the heart of the system, all the components of a CM system are critical. The purpose of this component is to: Maintain and control configuration baselines (known and defined states) Document and […]

MIL-STD-973 lists configuration identification as the first step in the configuration management (CM) process. We do not think this is some bureaucratic whim, but rather, one of the most important components of CM. Are speaking about systems, subsystems, components, parts, software revisions, and more? The simple answer is, yes! To avoid confusion when using bills […]