[SATLUG] Re: XP/Agile vs. CMMI (was Re: SLOC was Re: PHP Eats Rails...)

[Bruce Dubbs]

Justizin wrote:

> The problem with big design is that needs change and people often
> mis-state requirements.  If you can get something in someone's hands,
> you can move forward.

You are talking about the waterfall model here and that is definitely
not synonymous with CMMI.   The spiral model, for instance, say to do
exactly what you are advocating.

> CMMI is antithetical to agile.  it's fat and slow by definition, and
> that doesn't work for any industry these days.

Not really.  It does expect you to do documentation and testing though.
 It also wants you to measure what you are doing.  It can be customized
(the intent is for it to be) for most development models.

I don't think the ideas you advocate are appropriate for systems where
failures mean that people may die or equipment worth millions may be
destroyed.

  -- Bruce