Prune Me, Please
In “Integrating CMMI and Agile Development“, Paul E. McMahon asserts that even though they’d like to, many orgs don’t “prune” their fatty, inefficient, and costly processes because:
..it requires a commitment of the time of key people in the organization who really use the processes. Usually these people are just too busy with direct contract work and the priority doesn’t allow this to happen.
One of BD00’s heroes, the Oracle of Omaha, has a different take on it:
There seems to be some perverse human characteristic that likes to make easy things difficult. – Warren Buffet
Of course, both reasons could apply.
Leave a Reply
Why am I here?
WTF?
Meh!
D'oh!
My BTC Address
Bulldozer00's Blog 
Good post. I agree with both arguments.
My last company’s QMS had this problem in spades. I’ll add a variant problem. The people writing the SOP’s aren’t trained how. Interestingly, in their case, the people who did the actual work wrote the initial processes, but weren’t trained on how to separate the wheat from the chaff.
As a result, the procedures, templates and work instructions were too specific to one instance of the problem. It’s like having a Shape base class with lots of Triangle properties embedded, then trying to use it for Ellipses. And then you get the QA overseers who want you to follow the letter of the QMS.
Thanks for the great input CA. I hate trying to jam triangular pegs into elliptical holes.