IT Employment

Middle management trying to justify their existance again, huh?

Hello Binoy,

I'd be very interested to see if you had something different to say after you've been on a team of, say, 80-100 coders on a multi-million dollar project. Such projects in level 1 or 2 organizations are sheer ****; life gets a lot better for everyone for each level above that.

"Real IT persons" by the way are people who process help desk tickets, do app support for end-users, etc. They're not software developers. In typical corporate environments IT persons never cut code except to smash together a perl script for some admin task. If that's the context you are talking about, then much of the documentation you are referring to would be overkill. I'll grant you that.

Best.

--Casey

We try to make it clear to people that the CMM has a purpose, one that they agree with. That following the CMM slavishly as if it were a cookbook so that the purpose is sabotaged is not the way to do it. Almost every single activity in the CMM is optional. You're supposed to use it as a guide to identify the areas in which your organization is weak, and strengthen them.

Someone said that at the lower CMM levels, IT shops spend more time on value-adding endeavors. That's true. They certainly spend almost no time on reporting, measuring, improving, and most of the other verbs that constitute the dictionary definition of "manage." What you don't say is how little value those remaining tasks add when they're not being managed well.

A good percentage of America's software "developers" are sidetracked into repairing software defects that could have been easily prevented by requirements and code inspections, and into projects whose ultimate failure could have been easily foreseen by a rudimentary risk analysis. But until the day that the software crashes in production or the project is cancelled, the people who build such software believe they are adding value.