Agile Methodologies NOT for Large-Scale Projects

[chris payne]

Agile Methodologies in Large-Scale Projects: A Recipe for Disaster

The four “Agile Values” written within the Agile Manifesto are as follows:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

The values above are to be interpreted in such a way as to value the notions on the left-hand side of the “over” more than those on the right hand side. I propose, however, that in large-scale software development, this is infeasible, and that the left-hand side of each of these values (which are more akin to traditional development models) are far more appropriate in such projects..... Here is the link to the whole article:

https://blog.inf.ed.ac.uk/sapm/2014/02/ ... -disaster/

[Derek_Thomas]

It looks to me that someone might have an ax to grind here

[chris payne]

Hey, don't shoot the messenger I was simply posting what someone a lot more knowledgeable than me posted on the subject.

[Derek_Thomas]

Well, it was interesting that you posted the link to the article, but you did not mention the "response" article,

https://blog.inf.ed.ac.uk/sapm/2014/03/ ... -disaster/

Don't you think?

[PatrickNorris]

Chris:

I have been using Agile methodologies (in particular Scrum) for software development for many years and I can tell you that it if it is applied correctly it works for small and LARGE projects alike.

And, this is not some theoretical claim, it's based on real-life experience!

[chris payne]

I am not knowledgeable enough to know one way or the other, so I will take your word for it. All I was doing was pointing out what some "other" expert was saying, that's all!

[Andrew.Hillipar]

Agile methodology is actually very well suited for very large projects. It's all in how these methodologies are implemented!