Exploring Solution Spaces © Copyright 2003-2006, by C. Keith Ray
   


About
Exploring Solution Spaces, Keith Ray's blog on Software development and other topics.

Send comments to:
keithray@mac.com

For Agile Training, eLearning, or Coaching contact:
Industrial Logic, Inc.
866-540-8336 (toll free)
510-540-8336 (Berkeley, California)

Links
xpminifaq
Résumé
“Adopting XP” Article 2002 (pdf)
“ Refactoring” Article 2006
AYE Conference
Lucien W. Dupont
Elisabeth Hendrickson
Johanna Rothman's Managing Product Development
Brian Marick's Exploration Through Example
Esther Derby's Insights You Can Use
Laurent Bossavit's Incipient(thoughts)
Dale Emery's Conversations with Dale
Martin Fowler's Bliki
Creating Passionate Users

Archives

  • 2003
  • 2004
  • 2005
  • 2006
  • 2007
  • 2008
  • Subscribe
    RSS Exploring Solution Spaces XML


           
    2003.May.15 Thu

    Agile Project Management Paper and Statistics

    Get a free copy of a Cutter Consortium report: "Agile Project Management: Principles and Tools", by Jim Highsmith, at http://www.cutter.com/offers/APM.html. Forty pages, well worth reading (and a "$150 value!").

    A few quotes from that report:

    On agility: "We are no longer talking about 15%-20% scope creep on projects; we are talking about everything - scope, features, technology, architecture - changing within the span of six months.... The traditional project management maxim of 'conforming to plan' fails dramatically in these situations."

    On traditional project management, he quotes someone in the construction industry saying "The ... PMBOK... is based on two underlying theories: management-as-planning, ... and the thermostat model... both theories can be shown to be heroically simplistic and insufficient from the point of view of project management reality."

    Highsmith describes the "agile project management model" with a graphic that I'm trying to reproduce in text form here:

  • 1. Envision
  • 2. Speculate (create Feature List and Feature Plan)
  • 3. Iteratively Deliver Features (from Feature Plan, create Tested Features)
  • 4. Monitor and Adapt (from Tested Features, create Final Product, Adaptations jump back to Speculate)
  • 5. Close
  • Traditional project management focuses on activities, while agile project management focuses on delivery. Highsmith writes "Teams that focus on activities get lost, and even worse, they often don't realize it. Earned value analysis ... has nothing to do with value but with cost accounting based on planned tasks versus actual tasks. The value of what those tasks actually deliver gets lost."

    Cutter also has a survey paper here that I summarize below:

    Survey of 200 IS/IT managers

    Location

  • 33% North America
  • 20% Europe
  • 10% Australia
  • 8% India
  • 8% Asia
  • Industry

  • 39% software companies
  • 11% financial services
  • 9% consulting or like services
  • 6% state or national governments
  • 5% telecommunications
  • Heavy Methods in use...

  • 51% RUP
  • 27% CMM-compliant (!?)
  • 26% ISO-9000 compliant (!?)
  • Agile Methods in use...

  • 54% in-house developed agile method
  • 38% Extreme Programming
  • 23% Feature-Driven Development
  • 22% Adaptive Software Development
  • 19% Dynamic Systems Development
  • 9% other
  • 8% Crystal Clear
  • 7% Lean Development
  • 3% Scrum
  • This article predicts that 50% of companies will have some agile projects "by 2003".

    The bit about CMM and ISO-9000 as heavy-weight methods is a bit confusing, since compliance with those standards doesn't necessarily require forgoing an agile process.

    [/docs] permanent link