Agile vs CMMI
There is a lot of angst and anger generated as to whether the Agile methodology or more formal methodologies like CMMI are 'right' for software. Then there is the crowd that pulls the term 'methodology' further apart, into 'framework' and 'process'. Hoo boy! In an article by Sarah Sheard, draws your attention to the fact that there is no silver bullet (heard this one before?) with regard to methodology / process / whatever.
Unfortunately, there are businesses dedicated to selling training or certification, and therefore they have an active interest in clouding the water. (Not that cloud!)
Steve McConnell in his 1993 book Code Complete says - Design is a sloppy and wicked process - sloppy because the right answer is hard to distinguish from the wrong ones; wicked because the problem can only be solved by being solved. This problem of design I think can refer to IT&C strategy too. He may well be stating the same thing as Sheard when he makes this claim.
I cannot think of a worse way to encourage innovation less, than to inflict CMMI on a fledgling industry. Conversely, the discipline of CMMI is essential in building the industry.


