Applying Lean Principles to ITIL Event Management Process

Configurations Management in itself is a supporting discipline not delivering any direct clients value. However if we revolve it around a bit and look at the Configurations Management methods as the deliverable? Being careful not to sub-optimize, we could ask ourselves who is the customer and end user of the Configurations Management process? And what is value to them? 
In a project the Software development group is the principal customer and user of the Configurations Management methods. There are yet many more stakeholders which promote the Configurations Management discipline, similar to project managers, product management etc and ultimately the end user/customer. Value, chiefly to the Software development team, other than also the other stakeholders, should be a visible and streamlined Configurations Management process which permits them to develop characteristics rapid with the intention to fulfill their key task that is to deliver value to their customer, the end user. It shows that Configurations Management must support and help the project to deliver customer value more quickly.
Brief accounts of seven principles of lean software development from a Configurations Management viewpoint are as below: 

Eliminate Waste: – In this identifying and eliminating needless waste. When it comes to Configurations Management a usual source for waste is the Change Control Board (CCB). 

Build Quality In – In this building quality software development is utilized into the process/product in its place of adding it in a test phase at the end. A lean approach would be to help to avert imperfection through searching and fixing them before they end up as defects in a test phase. 

Create Knowledge – Feedback is information, and to get information during feedback we have to recognize the feedback regularly and run them frequently. This means which the Configurations Management infrastructure should permit frequent liberates, with an efficient build process and frequent integrations among parallel activities. An efficient agile build process utilizes incessant integration and automatic testing enabling instant feedback to the developer and software development , in addition to frequent deliveries, and feedback, to the customer.

Defer Commitment – in this we should never take decisions until we are need of that. When that last accountable moment happens we have the large information to make our decision.

Deliver Fast – For some reason it has been extensive in the software industry which if we perform things unhurried and cautious we will get higher quality, particularly when it comes to needs software development gathering. Therefore if we in its place