In my reading and research… this article’s title surely got my attention:Stop with the Lessons Learned…Correct me if I am wrong but it seems to me that the……

In my reading and research… this article’s title surely got my attention:Stop with the Lessons Learned…Correct me if I am wrong but it seems to me that the……

I get many comments during my coaching sessions, at conferences and within networking groups, about understanding Configuration Management and the System/Software Development Life Cycle (SDLC). Once these individuals read: A Practical Guide to Understand and Apply “Software/Firmware Configuration Management” – Within the System Development Process, they began to understand how valuable it is to understand Configuration Management and the System/Software Development Life Cycle. Many also stated that additional information in this newsletter, was significant and reinforced the value of Configuration Management within the SDLC.

I appreciate you providing the link to the SOP.
After reading the SOP identified for Configuration Management and paying particular attention to the definition, it is not describing the Configuration Management that has been known for years in industries such as Aerospace and DOD. Configuration management is now being used (or attempting to be used) in the commercial IT industry.

Your SOP relates to a platform/infrastructure for environments (e.g., development, test, etc.). It is good information for that topic and releases supported by those environments but it is NOT “Configuration Management” as the industry knows it.

The book referenced above is an excellent source to understand Configuration Management, its definition and concept while also understanding the system/software development life cycle (SDLC).

Note: Understanding Configuration Management also provides you the process to identify product (system, software, etc) deliverables for the development life cycle.

First, here is the definition of Configuration;

“Configuration, the functional and physical characteristics of hardware, firmware, software, or a combination thereof as set forth in technical documentation and achieved in a product.”

Configuration Management begins with requirements.

In addition here are two related articles for further reading.

Understanding Configuration Management
Configuration Management Clarified

The former also identifies problems and issues and provides a solution to correct the problem of misunderstanding and the improper application of Configuration Management.

My comments are being provided because of my concern for individuals, organizations and companies not understanding CM, how to apply it and how it applies to the SDLC.

And Bob, CM and QA complement one another and without good CM and QA, planned and implemented for a program or project’s development process, the project and program will become troubled and/or fail.

Keep in touch because I provide coaching and mentoring. Click Here To Contact…

Just because ERP may be a great idea for one organization does not mean it is a great idea for ALL organizations.

Before the attempt to install ERP was made was there a study to determine the need? The first step in all projects should be to determine what is needed and then develop a solution to fulfill the need. NOT begin with a solution and then try to fit it to a need that is not there.

First step seems to have been ignored.