The Enterprise Dilettante is named "project leader" for the "maturity model" project for a relatively new outfit named OWASP - why does the acronym remind me of a venomous insect, and not an internationally recognized standards body?
Why would an organization led by people who recently claimed that requirements are best (and only) expressed in software code (here's a hint Jimbo: non-IT people don't think in terms of object orientation), not in written/spoken languages - like English - that most people comprehend, need a maturity model? It goes against the grain of everything he stands for: like "strong technical leadership," and "people over process," "working software over comprehensive documentation," and "process weight," among other tired trials and tribulations that he continuously espouses.
I wonder what he'll do about contributions to this "effort," particularly code, from India, or eastern Europe. Since they don't make over 100K USD/year over there like he does, he'll overlook that minor point, yet rail about offshoring even though current IT employment in the US is higher now in 2008 than it was before the dot-bomb implosion earlier in this decade.
So Jimbo, what's your "maturity model" going to look like? Code? Process (heaven forbid)? Powerpoint (OMG)? How heavy is it? How light? How constrained by the Agile Manifesto? Or not? Bottom line dude: who does it successfully serve?
It's one thing to get on a soap box and bleat endless platitudes that in the end mean nothing to anyone. On the other hand, if you have something of value to deliver...we're waiting, but not holding our collective breath.
Show me - and I'm betting that you can't.
Comments