This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: CMMI and other processes - who needs 'em?
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple.
This blog is about how I do it.
Joel Semeniuk owns up to his secret love - CMMI. So I thought I'd respond with a double counter. CMMI, and its ancestors for that matter, have always leaned toward the "process" side of the People-Process spectrum. The rise of the agile methodologies is something of a collective recoil from process-heavy methodologies. If I had to sum up a lot of the experiences developers have had in process heavy environments I think that this would be it: "Well, finished THAT document, now I get to fill in THIS OTHER form."
I don't think that I need to get into the advantages of agile methods, there is already so much out there. However, after this somewhat superficial first counter, I thought I'd counter the counter.
There is method to the madness. No, wait, strike that. There is madness to the method. No, that isn't right either. Screw it.
Ask a pro golfer to document, in detail, every single step of everything he does to win a golf tournament. Take that huge document, and give it to someone who never played golf before. Chances are...
Previous Topic
