|
Tuesday, March 09, 2004 |
|
Is CMM an enabler or a director? Reflecting on Martin Fowler's piece about Software Development Attitudes I found myself wondering, "is CMM an enabler or a director?" It's probably a bit of both. I'd sure like to get rid of all the directing stuff. The superfluous directing processes frustrate me. They prevent me from doing the right thing and often force me to do more paperwork than is really necessary. CMM also seems to foster this notion that creating processes is always a good thing. Case in point: One of our content management groups just finished an eight-page document outlining the process for deploying content from an Interwoven TeamSite repository. That's ridiculous; it just isn't that hard to do. We might be better off focusing on explaining what to do and eliminate the detail on how to get the job done. Maybe that's the difference between enabling and directing.
Final Thought: When we create processes specifically to ensure that lesser developers are forced into meeting expectations, we are solving the wrong problem. 4:18:13 PM 
|
|
Do you enable or direct? Many debates in software development are underpinned by whether the speaker has a DirectingAttitude or an EnablingAttitude. These different attitudes affect choices over languages, designs, tools, processes, and lots more....
I really like what Martin has to say here, probably because I am an enabler and get very frustrated with those who prefer to direct. I'm also an optimist. I wonder if being an optimist and an enabler go hand in hand? 12:07:53 PM
|
