I am one of the
signatories of the Software Engineering Theory and Methods (SEMAT.org) initiative
started by Ivar Jacobson, Bertrand Meyer, and Richard Soley. In connection with
that, Capers Jones has been sharing with me some hard data summaries on a
variety of development methods and practices gathered from a very large number
of projects undertaken by varied organizations that contribute data on bugs,
costs, etc., to his company.
An interesting
thing is that agile methods fare better in most measures, including total cost
of ownership of final software product, than practices associated with CMM
level 3 but are NOT as good as the Rational Unified Process and all three are
trumped by CMM level 5. (The best practices, by a huge margin, are something else,
subject for a future post.) I don’t want to get into the specific numbers
(the data set is proprietary anyway) nor a long debate about research methods
or measures. It is just far to easy to quibble over and be distracted by such
matters.
I want to raise a
very different issue: What would it mean to the agile community IF these
findings really were valid and true? What if CMM level 5 and RUP practices
actually worked significantly better than agile ones? Would that mean we should
switch horses? Or would it mean we should revise agile to incorporate the best
parts of other practice traditions? (And maybe shed some baggage at the same
time?) Or doe the agile community have the TRUE answers, regardless of the
facts?
--Larry Constantine,
IDSA, ACM Fellow
Professor | University of Madeira | Funchal,
Portugal
Institute Fellow | Madeira Interactive Technologies Institute |
www.M-ITI.org
I am one of the signatories of the Software Engineering Theory and Methods (SEMAT.org) initiative started by Ivar Jacobson, Bertrand Meyer, and Richard Soley....
... Larry, I've been around the 'Agile world' for almost 10 years, and yet I don't believe that CMM level 5 or RUP are bad. I have, however, witnessed people...
Hello Larry, I would like to think that I would switch if something better came along. In fact, Ron and I spend a great deal of our time looking for something...
Chet, We care in the development and certification of flight management systems, guidance navigation and control (CN&C), and command and data handling (C&DH). ...
and i would expect you to be doing the most agile development possible, and not doing wasteful process steps and losing money for no good reason other than...
Hello, Larry. On Friday, January 29, 2010, at 5:13:53 PM, you ... None of the above. (And the final question strikes me as a bit insulting, btw.) What one...
... That was certainly my thought. If I understand rightly, being CMM 5 requires certification, while "doing Agile" is a self-designated label. My sample size...
William, You may be confusing development methods with maturity assessment process. CMMI (not CMM) is a set of Process Areas used to assess the maturity of the...
Larry said "CMM Level 5". Was he referring to CMMI or CMM? I took it that he meant CMM because he said, "The best practices, by a huge margin, are something...
Thanks, Glen. I'm aware of their nominal orthogonality, but Caspers and Larry are treating them at least somewhat differently. The spreadsheet Caspers sent me...
William, The only people I know are aerospace and defense. We work programs in those sectors. Some enterprise IT (health insurance) on the other side of our ...
... Thanks, Glen. I'll take a look. ... Well, there's failure and then there's failure. System breakage is one kind of failure, and I agree for a lot of people...
... Interesting bit of trivia -- Krantz didn't actually say that originally. He used it as a book title after the line became associated with him in popular...
Michael, Correct, it's the title of a book. But having sat in front of Krantz and Lovell they have now incorporated the myth into the "story." Lovell's quote ...
Glen, In Lovell's case, survival depended on success and it was reactive. I also remember that Capt. Haines & crew managed to get their crippled United Flight...
... This is a great case study of the kind of collaboration we want to create on agile teams. For those who haven't read it, the crew made the best of a...
... +1 Having done aerospace embedded systems for most of the 80s and 90s, and now Scrum, I'd probably use Scrum with an extraordinarily rigorous definition of...
... I think that's a great point, and it matches up with something I've been thinking about lately. (And talking about with Jeff Patton just last night, so...
... This discussion reminds me of a particular incident building one of the thousand subsystems on an airliner in the early 90s. One of the good things about...
... I think it started here just because Larry sees himself as user-focused person, so this list is his connection to the Agile community. However, I'm hoping...
... ... This reminds me that the way we work can be strongly influenced by the incentives that affect us. In the sort of environment you're describing, a...
Great post, Dave. ... This is true, but my point in mentioning this is that if you have a culture that's about blame, then Agile methods are a poor fit. Agile ...
... "Waterfall" didn't cause blame-ducking behavior, and "agile" doesn't cure it. It's a question of organizational culture and values. ... The key words IMHO...
... Sure. But using a few Agile techniques, IMHO, doesn't make you Agile. Which wouldn't matter a lot. Except that people like Capers are drawing conclusions...
... Well, IMO it /doesn't/ matter a lot. I think our goal is to improve the effectiveness of software delivery, or more to the point, value delivery through...
Hello, davenicolette. On Monday, February 1, 2010, at 7:40:24 PM, ... Capers Jones has collected more data about real software projects over many more years...