Wow, it’s been a long while since I’ve posted. It’s been a busy couple of years working with the configuration management capabilities in the IBM Collaborative Lifecycle Management and IoT Continuous Engineering solutions!
In my last post, we had just introduced these new capabilities to the market. There was considerable interest, but initial adoption was slow… many clients weren’t ready to take on the process transformation that goes along with using configurations, while others required additional capabilities. Two years later, the solution has advanced significantly, a number of clients have successfully implemented the capabilities in production, and interest continues to grow.
So what have we learned over this time? Our original guidance was to go slow: ensure you have a good understanding of your current process, the new capabilities of the solution, and take the time to work out what your new practices will be in light of those capabilities. It turns out that is good advice that still applies. Configuration management introduces new concepts, operations, roles, applications… there’s no way you can just “turn it on” and continue working the way you always have. To be successful, you need to take the time to plan and pilot your adoption.
We’ve begun identifying some patterns based on what we’ve observed at clients who have implemented configuration management — including what worked and what didn’t — and articulating some additional guidance around adoption. The initial set of articles is now available on Jazz.net, focusing on general guidance, component strategy, and stream patterns:
- CLM configuration management: Adoption guidance and practices
- CLM configuration management: Defining your component strategy
- CLM configuration management: Patterns for stream usage
- CLM configuration management: Single stream strategy
- CLM configuration management: Multistream variant strategy
- CLM configuration management: Multistream concurrent release development strategy
We plan to expand this series to address additional topics that might include baseline strategy, change management, and additional stream patterns.
We welcome your feedback and input on what to cover in future articles: what burning questions do you have about configuration management? Are there particular topics that you’re struggling with? Let us know. We hope you find these articles useful.