Multidimensional Methodologies

In preparation for the upcoming SPIN panel the (common) question was asked. "Is there a continuum with Waterfall on one end and Agile on the other?" My response is that the differences are multidimensional and relate more to where you are and where you want to go. So I came up with a way to look at various different software development methodologies and came up with this.

I'm still working on the significance (if any). In any case a few observations:

  • Moving from an ad hoc process to any other process will be difficult since so many dimensions have to change.
  • Moving between the agile processes (FDD, XP, Scrum, Crystal) won't be so difficult since few dimensions have to change.
  • Scrum being mostly a project management method has an unusual shape and combining it with any of the others causes its diagram to flesh out.

I'm sure there is more work/analysis to be done in this area. Anyone seen this before? Or have observations of their own?

Published Wednesday, September 29, 2004 2:45 PM by Wayne Allen
Filed under:

Comments

# re: Multidimensional Methodologies

I think that many believe there is a continuum between plan-driven and agile methods, with iterative development partially overlaid on such a line. Plan-driven process improvement models such as CMMI have moved to introduce iterative, adaptive development, and agile methods are acknowledging that process must be introduced in order to support anything other than small scale development.

And yes, Barry Boehme and Richard Turner (amongst others) have performed similar analysis to you - albeit using different criteria than your own.

I'm not sure your identifying those factors critical to discriminating between plan-driven or agile approaches from a project success perspective. They, however, are more helpful when perhaps comparing agile methods with each other. Mixing the two on this basis might not be taken too seriously, by those involved in large scale development ;)

That goes to including a "waterfall" method in your analysis. Much better to explicitly include say SW-CMM, CMMI, PSP/TSP and SPICE explicitly.

What's a SPIN panel?

Thursday, September 30, 2004 12:50 AM by Alex Hoffman

# Picture's worth a thousand words

Hi Jake... what an interesting diagram.

This sounds similar to the kind of analysis Alistair Cockburn does... I'm not sure how your variables correlate to his in Agile Software Development, though.

When you're happy with it, if you'd like to package it up with your commentary, I suspect the Agile Alliance would be happy to review and post it. I help out on the editorial team - feel free to send it to me if you like.

http://wiki.scrums.org/index.cgi?DeborahHartmann

Deb H.
Certified ScrumMaster/Practicing

Thursday, September 30, 2004 7:30 PM by debhart9

# Getting feedback

Oh, and: You might get some interesting feedback from the members of the ScrumDevelopment list... if you are interested.

http://groups.yahoo.com/group/scrumdevelopment/

Thursday, September 30, 2004 7:35 PM by debhart0

Leave a Comment

(required) 
(required) 
(optional)
(required)