Stories
Slash Boxes
Comments

SoylentNews is people

posted by CoolHand on Friday May 08 2015, @11:26PM   Printer-friendly
from the coding-for-dollars dept.

Andy Hunt - one of the originators of the Agile Manifesto, and NOT your humble submitter - has concluded that Agile has lost its way:

in the 14 years since then, we‘ve lost our way. The word “agile” has become sloganized; meaningless at best, jingoist at worst. We have large swaths of people doing “flacid agile,” a half-hearted attempt at following a few select software development practices, poorly. We have scads of vocal agile zealots—as per the definition that a zealot is one who redoubles their effort after they've forgotten their aim.

And worst of all, agile methods themselves have not been agile. Now there‘s an irony for you.

How did we get into this mess?

The basis of an agile approach is to embrace change; to be aware of changes to the product under development, the needs and wishes of the users, the environment, the competition, the market, the technology; all of these can be volatile fountains of change. To embrace the flood of changes, agile methods advise us to “inspect and adapt.” That is, to figure out what‘s changed and adapt to it by changing our methods, refactoring our code, collaborating with our customers, and so on. But most agile adopters simply can‘t do that, for a very good reason. When you are first learning a new skill—a new programming language, or a new technique, or a new development method—you do not yet have the experience, mental models, or ability to handle an abstract concept such as “inspect and adapt.” Those abilities are only present in practitioners with much more experience, at higher skill levels

Andy also has some thoughts on how to correct this - starting with the idea that Agile methodologies must be applied to Agile methodologies, to allow them to adapt to changing needs.

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by Nerdfest on Saturday May 09 2015, @01:44AM

    by Nerdfest (80) on Saturday May 09 2015, @01:44AM (#180597)

    Pair programming is great, but draining. I find that I can't do it all the time. I've found that Agile works very well, but often it's used as an exclude for poor specs. Even then it would work except that everyone seems to keep wanting to pull back into waterfall all of the time which demonstrably does not work when you don't have a clear predefined set of requirements.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2