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
Thread beginning with comment 448318
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: terrible article
by Tuishimi on Wed 3rd Nov 2010 06:52 UTC in reply to "RE[2]: terrible article"
Tuishimi
Member since:
2005-07-06

I would have voted this up but I already commented...

I can see that agile has benefits but only if it is done right and if everyone involved in a project knows and understands the process and tools well.

I come from the "old school" ways... it has been difficult but not impossible for me to latch onto this, but even I, with my minimal knowledge, see the process totally abused on a day to day basis... And let me tell you... a project run under the "agile" moniker but not REALLY is PAINFUL. I am in one of those right now.

Scrums break down into technical discussions, sprint planning becomes "this is what you all need to have done for this sprint"... etc.

I'd much rather do it the old way, spend time up front to use the old input-output requirements, functional specs/flow charts and design specs BEFORE we start coding so that it is clear as to what needs to be done.

No fancy terminology, meetings circumscribed by their purpose as they always were, development cycles demarked simply by deliverables, etc.

Now, I KNOW the agile process defines these things, but unless a company commits 100% to learn and implement it, it's useless.

Reply Parent Score: 5