This article discusses the importance of effectively communicating the value of Configuration Management (CM) systems to executives, particularly in the context of preventing costly product recalls. It highlights the financial implications of recalls in the automotive and medical device industries, advocating for CM2 principles as a strategy for risk mitigation and protecting brand value.
This article discusses the misconceptions surrounding Configuration Management (CM), emphasizing that poor CM practices cause delays, not CM itself. By adopting proper CM2 strategies—like early baselining, clear ownership, and standardized processes—organizations can enhance efficiency and agility in development. The piece encourages reader engagement and highlights the importance of process excellence.
The blog post discusses challenges in achieving just-in-time document release, emphasizing common issues such as lack of control over timelines, weak change authority, and informal workarounds. It outlines practical steps for improvement, advocating for defined roles, effective planning, and treating deviations as signals for process gaps, thereby enhancing configuration management.
This article emphasizes the importance of “Just-in-Time” document release in project management. By releasing documents only when needed, it minimizes waste, enhances agility, and reduces risk of using outdated information. The author advocates for structured release mechanisms and synchronization with workflows to improve clarity, accountability, and overall project efficiency.
In A Christmas Carol, Scrooge is visited by three spirits who show him the consequences of his choices and the benefits of change. I often think about how this idea applies to Configuration Management (CM) as well.
Many people think creativity and discipline sit on opposite ends of the spectrum. Do you think discipline kills creativity?
Think again. The most innovative organizations know that structure isn’t the enemy. It’s the enabler. So, you could say Discipline and Creativity are best friends.
In this month’s feature article, I explored “The Real Job Description of a Configuration Manager.” But let’s flip the lens and talk about what a Configuration Manager is not.
What is the quality level of the product data in your organization?
🤥100%? — You’re lying to yourself.
✅99%? — Hard to believe.
🆗95%? — Impressive, but not enough.
❌Less than 95%? — That’s the reality for most organizations.
Let’s be honest, when many people hear “Configuration Management”, their first reaction isn’t excitement. It’s usually something like:
“That’s bureaucracy.”
“That slows us down.”
“That’s for documentation people.”
Let’s talk about a pattern I’ve seen in too many organizations, one that quietly kills morale and reinforces the wrong behaviors.