Linked by snydeq on Tue 2nd Nov 2010 23:08 UTC
General Development InfoWorld offers a look back at the first decade of agile programming. Forged in February 2001 when a group of developers convened in Utah to find an alternative to documentation-driven, 'heavyweight' software development practices, The Manifesto for Agile Software Development sought to promote processes that accommodate changing requirements, collaboration with customers, and delivery of software in short iterations. Fast-forward a decade, and agile software development is becoming increasingly commonplace, with software firms adopting agile offshoots such as Scrum, Extreme Programming, and Kanban - a trend some see benefiting software development overall
Permalink for comment 448311
To read all comments associated with this story, please click here.
RE[2]: terrible article
by Gunderwo on Wed 3rd Nov 2010 05:05 UTC in reply to "RE: terrible article"
Member since:

In my experience there are a lot of companies that say they use Agile methodologies and do TDD when all they're doing is paying lip service to the buzz words that make them feel better.

In order for agile methods to work the developers and managers need to actually understand the how, and why of each step and do it right otherwise it's just adding extra overhead.

I've worked at several places that will SCRUM but then never do burndowns and calculate velocities. Or think that because they didn't get everything done in a sprint they can just add the missed tasks to the next sprint and end up in the same place at the end of the next one.

Bad management is bad management no matter what the buzzword methodology being used. And bad developers will always be bad developers if they don't try and learn how to become better.

Edited 2010-11-03 05:06 UTC

Reply Parent Score: 8