This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.
This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.
Freshness Warning
This article is over 9 years old. It's possible that the information you read below isn't current.
13 Sep 2002
New Architect’s October issue has an article called Scaling Agile Methods about using aglile development methods like Extreme Programming (XP) in large development teams. The commonly held belief is that agile methods only work well when a project has a small (less than 12 or so) development team, and this article attempts to refute that.
It wold be interesting to see a case study of a project where agile methods were successfully employed on a large project, but this isn’t it.
The author used XP on a development project, but he only provides three paragraphs about the success of the project, an one of those is a simple rehash of the goals of XP.
In order to prove that XP works, the author relies on anectdotes. "Based on my experience, agile methodologies do work. In fact, I’ve found them to be just as effective as traditional ones." Why would a development team try a new methodology that is unproven in large projects if it is only "just as effective" as the one they are already using?
He also presents arguements as fact with no supporting eveidence. "If you’re moving to a new technology platform or your project calls for fluid requirements, these older [traditional development] methods aren’t suitable." That may come as a surprise to development teams that have successfully performed these tasks using traditional methods.
Has anyone seen a case study or paper on the use of a particilar agile methodology on a large project?
CMM isn’t a development methodology per se. It is a means of rating the quality of a development organization. Using the CMM, you have a standard by which to judge yourself and a measuring stick to use in comparing yourself to others.
One of the problems I have with CMM isn’t the concept itself, but the way it is applied in many organizations. Just as with ISO 9000, TQM, or other quality benchmarks, organizations tend to get bogged down in the specifics of the process rather than the results.
A project that delivers on time, under budget, and exceeds client expectations is considered a failure if the Process wasn’t followed to the letter. If a project isn’t a success, it is blamed on not following the Process.
The other thing that happens in companies that worship the CMM is they often treat programmers as interchangable resources. It is a mistake to treat your programmers as blocks of time instead of skilled thinkers. If you don’t pay attention to the individual talents of your developers you will have consistently late projects. You need to match your developers to the problem being solved.
All that said, I really enjoyed those two articles. It’s interesting to read how XP practitioners see themselves fitting into the CMM.
you’re spot on with your comments.
i was a little loose with my language. as you correctly point out, cmm is, stricly speaking, a model for “modeling, defining and measuring” the maturity of software processes. i tend to think of it as being interwoven with a set of management practices that dictate how to manage software projects for a given sei level, including the selection of the appropriate software development methodology for the project at hand - be it RUP, RUP-lite, waterfall, or xp.
the point, which was admittedly tangential to your initial question of whether or not xp was being used for large projects, was that for most large companies that develop large projects, agile methods will likely be wedged into existing management structures like the cmm and it’s interesting to see how that “evolution” is taking place.
to directly answer your question, from my own experience, companies are still getting their feet wet with figuring out how/when agile methods are appropriate. and most companies will do something like look at the size of the required team and the number of sites to dictate the appropriate development methodology [i.e. see figure 2 http://www-106.ibm.com/developerworks/library/j-j1preview/index.html?dwzone=wireless ]. so, most big companies that are developing large projects are already on the path to making up their minds that xp isn’t appropriate for large projects anyway.
since i work for a large software development organization within an even larger technology congomerate that adheres to the tenets of the cmm, and has dabbled with agile development processes, i’d also be interested in finding out if anyone is using xp [ or related disciplines ] for large projects.
That’s a good point. The larger the organization, the more likely they are to follow (or attempt to follow) the guidelines of something like CMM. So how likely is it that a large team would even be given the chance to try out an agile methodology? CMM-centric organizations tend to resist anything that might be perceived as risk.
So that’s another thing I’d like to see adressed in an article on using XP on large projects. How did the project leaders convince their superiors to try an agile methodology. What are some good organizational and project indicators that can be used to identify whether the use of a lightweight development method will be successful?
Excerpt: An antipattern is a pattern that tells how to go from a problem to a bad solution. Listed below are links to some of my favorites....
Adam Kalsey
Mobile: 916.600.2497
Email: adam AT kalsey.com
AIM or Skype: akalsey
©1999-2012 Adam Kalsey.
Content management by Movable Type.
Eric Snowdeal
September 15, 2002 7:22 PM
while iit’s a little tangential to your main interest, there are a few public papers available that compare xp with the capability maturity model which is a methology that is often, for better or worse, used to manage large software projects [1-2].
[1] http://www.xprogramming.com/xpmag/xpandcmm.htm [2] http://www.sei.cmu.edu/cmm/papers/xp-cmm-paper.pdf