There are various ways of doing this but none of them are fool proof.
If your company has automation in place with any kind of mechanism that prevents unapproved deployments or changes to be made that is full of win. But few companies are to this point yet.
IMO, a super strict CM policy that is actively enforced can work, but can often just as easily work against. Creating a happy medium has worked great for my company. We had a "voice of the customer" customer being anyone who generates change activity to hear directly from them about what they like and hate about the CM policy itself. I'm sure you can guess that it was largely a bi*ch session.
But none the less that worked out VERY well. We took everything down and then reprioritized the concerns by severity and also by the most bang for the buck.
We then took that list and acted on it where we could. Its crucial to note that SOME things could not and would not be changed. They are requirements for a reason. This was not "lets make everyone happy" kind of thing and destroy the process altogether. This was lets make things better. We ended up streamlining a lot of things that were found to be redundant or "its this way because we just always did it this way".
In the end we came out with a better CM policy and by taking a huge number of our customers along for the ride and letting them drive conversations and such they felt better about CM too, and in turn adhere to the CM policy much, much better.
Another key ingredient is repercussion. If there is no repercussion for doing unauthorized changes then why would anyone feel they need to follow it right?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum