Talk:Agile software development/Archive 3

Archive 1

Archive 2

Archive 3

Agile impact on quality section would be nice

Just going a Google here and there one can find Agile advocates (a.k.a. religious proselytizers) suggesting that Agile software development processes do not adversely impact quality whereas one can also find Agile critics (a.k.a. David Hume-class Skeptics, capital "S") note that there is no body of metrics or suitable research which suggests that Agile processes (1) provide any value and (2) impact quality either way, beneficial or detrimental.

One of the problems I see just doing Google Scholar checks is that pale studies -- informal "at a glance" studies -- in to whether Agile processes contribute anything beneficial to software development are behind pay walls, the same goes for such Google Scholar-found publications which discuss Agile's impact on quality. All such studies are absolutely not scientific in any way.

For the extant article, it would be nice if there was a section that pulled together even the minimal research conducted in to whether Agile processes contribute anything or impact quality in any way. I would like to propose adding such a section complete with references and citations however linking to articles behind pay walls is prohibited, and the legitimacy of any such reference -- even to IEEE or the Journal for Computing Machinery -- are going to be biased.

What do you think? Damotclese (talk) 22:07, 7 June 2017 (UTC)

This article already contains a section for Criticism. If, as you suggest, you have evidence that agile approaches do not improve outcomes, or even that they make them worse, then I would suggest adding a sub-section to the criticism section, and exploring the ideas there. Be sure to include references, though, as anything critical that is unreferenced is sure to be reverted pretty quickly. I look forward to reviewing your contribution.

Incidentally, while you are right that you should not link directly to works behind a paywall, you can still cite those works -- much as you would for a book or other publication you would have to buy in physical form. They are all fair for citation and reference. Davidjcmorris  Talk  06:03, 12 June 2017 (UTC)

I'm not suggesting that Agile processes make quality worse. I'm noting that there is no science-based research that says that Agile works to improve quality or makes quality worse. Did you bother to read what I said? The question is whether the extant article should have verbiage noting that there is no science for this concept. Damotclese (talk) 14:55, 12 June 2017 (UTC)

Thank you, I did read what you wrote and, I think, resolved the concerns you voiced vis-a-vis articles that are behind a paywall, the ones that you felt you could not cite (whereas in fact you can). I welcomed your contribution and, I believe, was also quite supportive in terms of how to go about it. I did not intend my response to suggest your point to be purely about negative impact, although as I re-read it now I can see that is an interpretation of what I wrote. It would perhaps have been better written as, "if you have evidence that agile approaches neither improve outcomes nor make them worse then ...".

However, as you have highlighted your argument, let me pose a question for you: How are you be able to determine that there is no science available? If you have not accessed those articles behind a paywall, how are you able to determine that they are all pale studies (a rather pejorative term) and not scientific in any way?

To phrase this in a more scientific way: You cannot prove or disprove a null hypothesis without evidence. If you truly believe that there are no articles available that describe scientifically-based research into the impact of agile practices on quality, then you need to provide evidence for that viewpoint.

While you should not add content with unsubstantiated original opinion, you could instead add content that references others who claim there is no impact (as you did in your earlier comments), so long as you provide evidence that they said those things (in the form of citations). As I suggested, the appropriate place for this would be the criticism section. Davidjcmorris  Talk  02:01, 13 June 2017 (UTC)

That's just it, finding science-based research that cover impact on quality, research that is published on line, has been unsuccessful, Google Scholar points to non-scientific research involving asking polling questions from developers, and polls do not follow the Scientific Method. Point being that the extant article should note that there is no science which supports or detracts the ideologies of Agile process. Damotclese (talk) 14:10, 13 June 2017 (UTC)

Thanks. We should pause to consider the leap from an inability to find scientific research to saying that no scientific research exists. They do not equate. Some might consider it un-encyclopedic and un-scientific to say that they do, and making a statement that no scientific research exists is a pretty provocative statement to make when it cannot be evidenced. I think all we can really say is that you have so far been unable to find any scientific research. If you added that to the Criticism section, then if others know of some they can add references to it. This would not invalidate your initial assertion, that you have been unable to find any, and would move us on in a positive direction. Davidjcmorris  Talk  21:58, 13 June 2017 (UTC)

Separately, we could discuss research methodologies, as there are plenty of accepted qualitative approaches that construct hypothesis and proofs from interviews and surveys. This is perfectly acceptable, when it is done rigorously, especially in the social sciences. It is even better when this can be strengthened by quantitative evidence, which is probably the harder science you are after. I am confident that plenty of both types of research exist. I referenced some examples of each in my masters thesis on The Paradox of Agile Transformation: Why trying to be Agile stops organisations from becoming agile. I will look back to those, and other sources that I have to bring what light I can to your efforts. However, in the meantime, do not hesitate to add your comments to the Criticism section, as suggested multiple times above. Davidjcmorris  Talk  22:05, 13 June 2017 (UTC)

There is no scientific basis for Agile being better at quality or product development, no academic research has been done, there are no peer-reviewed journal entries that cover it. The OP noted that polls are conducted which solicit opinion, but that's not science. The article should probably note the fact but I expect that believers in Agile would revert such updates since Agile is a religion to believers in it. BiologistBabe (talk) 14:58, 14 June 2017 (UTC)

Two assertions without evidence.

1. No academic research has been done? Just a cursory glance at the public domain Google scholar, reveals over 200,000 entries on agile quality research. Some of those entries will be of questionable quality, for sure ... Google scholar does not have peer-reviewed checks on what it includes ... but I can see entries that link through to academic papers and peer-reviewed articles on the impact of agile practices on quality. I also know that running the same search behind a university paywall would generate many more entries that would be more academic. If you put such an assertion into the article without references, then for sure it will be reverted, because personal opinion is not encyclopedic. However, if you can evidence that there is no scientific research, then please do add it to the criticism section. If you add an evidenced statement and it is reverted without warrant, then I give you my personal undertaking, for what that is worth, to protect its integrity until it can be refuted with evidence that there has been scientific research, academic papers, and peer-reviewed articles.
2. Agile is a religion? This is a tired cliché. While there are agilistas (the bane of my working day if I encounter one), there are far more pragmatic agile practitioners who recognize that the right approach depends on the context (and yes, a more planned up-front approach is appropriate at times). For example, check out the rigorously researched Cynefin framework from professor Dave Snowden. Davidjcmorris  Talk  18:03, 14 June 2017 (UTC)

Yes, exactly, Agile ideologies are not covered in peer-review journals even after 15 years, that's why there is no evidence that it works, no evidence that it does not work. That's why the extant article should have commentary about the lack of scientific validity. But as we can see, there is, as noted previously, a religious aspect to the belief that it improves product and quality, ergo we couls expect believers to not accept the lack of science... As we see in the talk page here. Damotclese (talk) 13:47, 15 June 2017 (UTC)

Maybe you can help me understand your viewpoint. I am someone who has lived through these changes. I see the benefits of a more planned approach for some types of work and a more exploratory approach for others. That is far from a religious belief, that is a pragmatic engineer's understanding that it is horses for courses. I started my working life in the 1980s as an IMB/370 Assembler programmer and then COBOL. Good times. The only prevailing methodology at the time was the staged approach, which is mostly referred to as waterfall these days. When our cycles were long, when technology seemed fixed, and when we thought we could lock down requirements at the outset, this seemed fine. After all it was the only thing we knew. It was that or follow no process at all. That too was OK for small systems but not for large complicated systems. Then ... new technology kept coming at us in wave after wave, markets kept changing their needs year by year and then more frequently. As the mix of our markets and technology became more complex, we needed a way of being able to respond more rapidly to these changes. Just In Time development and Rapid Application Development looked promising, The Unified Process, that was designed to evolve, was good too. But the cycle times were still too long. Then we got DSDM and Scrum and XP, and these were dramatic improvements. All of these were evolutionary steps, they built on the strengths of what came before, they equipped teams to cope with different circumstances. They got labelled as agile in 2001 by some guys on a mountain, but again this was a group of engineers figuring out how to build on what they knew. For some reason, every 5 years or so, as more and more organizations adopt more agile ways of working, it is described as all new. This is scary for some people. Then a lot of training firms, consultancy firms, and software toolkit providers got on the bandwagon, and of course their marketing engines took over. Four legs good, two legs bad. Everything that came before was evil, everything you do with the new way was good. Then they started in-fighting. To this old-hand, that was the most astonishing stage. To see the founders of Scrum denigrate the founders of SAFe was disappointing. To then see the founders of Scrum fall out and form their own separate associations was heart-rending. But I digress. Yes, for sure, there is a lot of heat and noise, fuss and nonsense written and spoken about agile practices. But those people do not represent the mainstream. They do not speak for me. Agile practices are no silver bullet. They will not make things magically better overnight. In fact, what many organizations struggle with is that adopting agile practices will expose organizational dysfunction, and that can be scary. And, more importantly, to this old pragmatic engineer, they are not appropriate at all times. I even wrote a blog on the research that waterfall was more effective than agile on very short projects. Can you please help me see where anything in this can be viewed as religious? Davidjcmorris  Talk  18:41, 15 June 2017 (UTC)

To move us on (if that is now possible). I am incredibly supportive of you adding this criticism into the article. I have pointed out the best section for it to go into. I have described how to cite material that is behind a paywall. My only advice to you was that your assertion should be referenced. That is sound encyclopedic practice. However, rather than just publish, you seem content here to keep repeating that there is no research, that nothing has been published in any peer-reviewed journals over the last 15 years. Unless you have evidence or references to corroborate that, all you can really do is express the opinion that you have not been able to find any yet rather than claim that none exists. Again that is the scientific way of describing your position (see my earlier point on the challenge of disproving a null hypothesis with no data). I would love to see that published, so that we can then see whether anyone in the community is able to find some (if it exists ... I think it does, but I cannot prove that yet). To help this, and avoid people just throwing out what you have described as pale research, perhaps you could take a moment to define more precisely what would you consider to be rigorous scientific research and what types of journals you would you consider to be valid and worthy. Davidjcmorris  Talk  18:50, 15 June 2017 (UTC)

Re-reading the original question, I returned to the main article and scrutinised it for assertions that agile practices have an impact on quality. There is no religious assertion that it has any impact. There is one reference to a claim in 2003 that agile practices improve quality, although no assertion is made that the claim is valid; it may be assumed by the reader that an absence of commentary on the claim leaves it standing as if it were commonly held to be true. There are also two somewhat hidden references to surveys in which people self-reported improvements. In light of this, I fail to see the level of passion expressed at the article. However, as stated above several times, the question poser is welcome to add a paragraph to the criticism section; so long as it is able to reference someone of renown who has this view and is able to point to where in this article any claims are made. Davidjcmorris  Talk  01:23, 18 June 2017 (UTC)

That is correct, there are no scientific studies that show that any of the so-called 'Agile' processes actually work, but that's the same for a lot of things that are basically religious beliefs which are marketed for profit. A good example is 'Common Core,' a set of religious beliefs that are sold to governmental educational entities under the non-scientific claims that it some how improves education and, ironically, reduces cost.

There is no evidence that Agile does anything useful or, for that matter, anything harmful. It is religion. The article should note that fact that there are as yet no science behind the claims Agile makes. TrainsOnTime (talk) 14:59, 29 June 2017 (UTC)

Thank you for adding your weight to the discussion. As neither of the previous contributors have yet been able to provide an adequate definition of what they meant by scientific studies, perhaps you would be willing to share you wisdom in this regard. If we can establish what the criteria are and what methodologies you would deem to be scientific enough, then we can embark on a reasoned and logical search and discuss the results of that. In best encyclopaedic etiquette of course. Let us please keep the baseless mud-slinging out of it. Thank you. Davidjcmorris  Talk  07:01, 30 June 2017 (UTC)

New lede section

I've re-written the lede; it still needs expansion in a few areas. Specifically, agile anti-patterns should be mentioned, or else that entire section should be moved to a sub-page. Also, something regarding "agile v. waterfall" might be added.

I don't think anything so far is controversial, but the changes in total are fairly large. Power~enwiki (talk) 23:07, 14 July 2017 (UTC)

Note by Edmonds

I've just removed the following text, added by Eaedmonds, which appears to be a personal anecdote relating to his 1974 paper in General Systems. While interesting, I don't think it's relevant or appropriate to have in the article proper, but I'm copying it here for posterity:

Note by Edmonds: I presented these ideas in London in 1970 and first submitted the paper to the Journal Computer Aided Design. It was rejected with the comment "If you don't know what you are going to do before you start you shouldn't start"! Only then did I submit it to General Systems.

—me_and 16:09, 14 November 2017 (UTC)

Capitalization of Agile?

The article mixes up capitalized and lower case spellings of Agile. There are other places that do the same.[[1]] Any thoughts on which is right? TimTempleton ^{(talk) (cont)} 22:15, 16 January 2018 (UTC)

The deliberate policy here is to use standard sentence case for the term 'agile' (leading capital at the start of a sentence, otherwise lower case), unless it is used in a title or proper noun (such as the Manifesto for Agile Software Development or Agile Alliance). Occasionally over-capitalisation creeps in, in which case we try to address that in a timely manner. Prompted by your question, I saw a couple of examples and fixed them. Thanks. Davidjcmorris  Talk  22:46, 16 January 2018 (UTC)

OK - thanks. Just checking because I saw another editor change to lower case elsewhere. TimTempleton ^{(talk) (cont)} 23:19, 16 January 2018 (UTC)

Missappropriations to unpublished manifesto: Is this an urban legend?

• User:Paulralph You said, "...evidence that Scrum increases productivity...". Who has investigated this and where did they publish the result?

mcyp (talk) 19:09, 1 September 2019 (UTC) FYI User Talk:JzG

• This article misapproriating the iterative development and evolutionary management as part of Agile. What is the connection? This is border line to 'fake news'. How can one appropriate former formal works from IBM where they are published to a unpublished manifesto? So called "Agile Manifesto" is a web document. To be honest, "agile software development" seems a bit of an urban legend went to main stream but no body knows what is it and anything and everything is agile. Unacceptable quality for a wikipedia article.

mcyp (talk) 19:09, 1 September 2019 (UTC) FYI User Talk:JzG

Changing the Article name to Agile Movement

I propose to change article name to "Agile movement" as this is a movement, as in social movement. This can not be presented as a development methodology as it did not grow out scientifically but a socially. mcyp (talk) 19:19, 1 September 2019 (UTC)

• That probably requires a request for comment. Please get consensus before making large scale changes. Thanks. Guy (Help!) 22:37, 1 September 2019 (UTC)

Wiki Education Foundation-supported course assignment

This article was the subject of a Wiki Education Foundation-supported course assignment, between 24 August 2020 and 16 October 2020. Further details are available on the course page. Student editor(s): Alexander.burkel.

Above undated message substituted from Template:Dashboard.wikiedu.org assignment by PrimeBOT (talk) 13:37, 16 January 2022 (UTC)

Low Quality Article

This article is too unscientific. It mostly regurgitates non-scientific professional literature, while ignoring relevant research. I'm going to add some research. If any agilisits out there take offence at my changes, please read the research before reverting anything.Paul Ralph (University of Auckland) (talk) 12:49, 5 February 2018 (UTC)

Please note that this content has been moved (rather than deleted); it is not significant enough in its own right to warrant being in the lead / lede paragraph. Also, the link you posted is to content behind a paywall; it's a bit hard if other editors are challenged to read this before they can challenge this edit. As it happens, my masters research topic was whether Agile Transformation worked or not, in which I referenced a paper by Dingsøyr which argued that agile practices do in fact help. I will reach out to you offline to suggest meeting up to discuss (as we know each other). Davidjcmorris  Talk  02:23, 7 February 2018 (UTC)

I never said that agile practices were devoid of benefits. There is, for example, evidence that Scrum increases productivity. I said there's no evidence that they increase agility. There are no validated measures of team agility, and you can't demonstrate a causal relationship on a dependent variable you can't measure. The fact that all these practices are called "agile" without anyone ever demonstrating that they increase agility is possibly the most important thing you could know about agile. It's like pfizer selling "cancer drugs" that don't fight cancer, or "anti-virals" that don't kill viruses. It's a "productivity practice" that doesn't increase productivity. It is very common on Wikipedia to point out the lack of scientific evidence supporting a thing in the introduction. And you don't get to discount research that's published behind a paywall. Paul Ralph (University of Auckland) (talk) 21:11, 7 February 2018 (UTC)

Can you clarify:

* What are you meaning by agility? Common uses included: Hypothesis driven experimentation, trying out ideas on a small scale. Early delivery of value (whether to customers / end-users or to the product owner / development team). Fast feedback to uncover change early and avoid too much investment in scope not required. The ability to absorb change without causing additional cost, by dropping lower priority scope. Etc. There is evidence that this happens.

* What you mean by scientific evidence? As Popper and others have said, it is hard to scientifically prove a hypothesis; so a theory should stand until there is evidence that disproves it. There is, however, an abundance of research in this field, following a wide range of research methodologies. Which methodologies would you regard as scientific and which not?

Incidentally, the research was not questioned, but rather the insistence that people read it before challenging the edit. The offer to discus the article and points raised in person still stands (I have emailed you separately about this). Davidjcmorris  Talk  01:26, 12 February 2018 (UTC)

Your conclusion about testing being performed during development as an agility indicator is false. Often testing happens at the end, but doesn't indicate agility 1 way or the other. What people call "Waterfall" now-a-days also had testing in it at various points along the dev life cycle (why "waterfall" is a misunderstood/derogatory misnomer). — Preceding unsigned comment added by 2603:9001:2708:7091:6C87:D82F:9846:8ADD (talk) 16:40, 9 August 2019 (UTC)

I know this is a slightly old debate but the biggest problem with this article is the lack of clarity. The introduction simply won't be understood by the vast majority of readers as it's full of buzzwords and never actually states in simple terms what agile software development is. It doesn't need more research, it needs someone who understands the topic and can write well for a general audience to edit it into something more useful to the target audience (i.e. people who don't already know what agile software development is). — Preceding unsigned comment added by 2A02:C7D:6623:9500:C866:C739:C5A0:3ACA (talk) 09:58, 8 June 2022 (UTC)

"work moves through software development lifecycle (SDLC) phases—with one phase being completed before another can start"

Agree. This is a farce that agile seems to actually need, to exist as a counter method. I've not seen waterfall used in commercial nor defense. 149.32.192.43 (talk) 16:27, 6 October 2022 (UTC)

"Snowbird summit" listed at Redirects for discussion

An editor has identified a potential problem with the redirect Snowbird summit and has thus listed it for discussion. This discussion will occur at Wikipedia:Redirects for discussion/Log/2022 December 14 § Snowbird summit until a consensus is reached, and readers of this page are welcome to contribute to the discussion. Rusalkii (talk) 04:39, 14 December 2022 (UTC)

Semi-protected edit request on 17 December 2022

{{subst:trim|1=

 Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate. RealAspects (talk) 08:11, 17 December 2022 (UTC)

Semi-protected edit request on 6 January 2023

Insert after "Arie van Bennekum": "(DSDM)" Nickdevoil (talk) 15:46, 6 January 2023 (UTC)

 Not done: please provide reliable sources that support the change you want to be made. ScottishFinnishRadish (talk) 15:56, 6 January 2023 (UTC)

In software development

In software development, agile (sometimes written Agile)[1] practices include requirements discovery and solutions improvement through the collaborative effort of self-organizing and cross-functional teams with their customer(s)/end user(s),[2] adaptive planning, evolutionary development, early delivery, continual improvement, and flexible responses to changes in requirements, capacity, and understanding of the problems to be solved.[3][4] Popularized in the 2001 Manifesto for Agile Software Development,[5] these values and principles were derived from and underpin a broad range of software development frameworks, including Scrum and Kanban.[6][7]

While there is much anecdotal evidence that adopting agile practices and values improves the effectiveness of software professionals, teams and organizations, the empirical evidence is mixed and hard to find.[8][9] 103.255.145.74 (talk) 14:16, 8 January 2023 (UTC)

First sentence is difficult to parse and not very informative

The article seems to have fallen victim to an effort to include every piece of information in the very first sentence, and I think the result is that the first sentence is a hard-to-read pile of jargon & buzzwords that doesn't actually tell me anything.

I'm not knowledgeable enough on the subject to fix it myself, but I feel the first sentence should state the primary goal of agile design. E.g. compared to other design paradigms, is agile specialized towards hitting a fast update cadence, keeping a large team organized, maintaining flexibility, or something else? Then the second and third sentences could provide non-exhaustive elaboration on techniques and philosophies used to achieve that goal. Being non-exhaustive is probably helpful there since the first few sentences are just introducing the reader to the subject. There's an entire article available to spend naming and explaining all of the details. Chris3145 (talk) 17:06, 5 May 2023 (UTC)

Difference between Process and Project

Agile is used to manage the production process of delivering products in the project according to Prince2, and it is not a project management methodology. It is complete nonsense to call the production process a project.

5. Managing product delivery (WP) - Managing product delivery (MP). Konsul28 (talk) 09:48, 23 May 2023 (UTC)

We follow the terms used by the reliable sources, not your personal opinions. MrOllie (talk) 20:29, 25 May 2023 (UTC)

Doubts about a reference

Hi, I am very interested in technology and computer issues. In my spare time, I read about related topics and, if I think it is necessary, I help to improve some wikipedia entries. About the "Agile Software Development" entry, I added a reference and someone reversed it. It is a reference that provides information about what is talking in the entry and improves it. I think it was because I added the reference wrong: I put "Cite web" instead of "Cite news," and I wrote the date wrong (for example: 07/06/2023, instead of 7 June 2023). I've corrected it, and I think it's correct now. Anyway, if it is wrong, you can correct it by yourselves without deleting it, so we all help to improve Wikipedia! ¡Thank you so much!

The reference is this one: https://www.elconfidencialdigital.com/articulo/noticias/metodologias-agiles-era-inteligencia-artificial-entrevista-arie-van-bennekum/20230607181016584992.html OnePapaya (talk) 14:15, 13 June 2023 (UTC)

It is redundant with other references - providing no new information. Given that, and given that this is the English language Wikipedia and the reference is not in English, it should be omitted. This has nothing to do with date formatting. MrOllie (talk) 14:27, 13 June 2023 (UTC)

Less marketing speak?

Reading over this article a few times, and this whole thing feels less like a plain explanation of a software development process and more along the lines of a cult recruitment manifesto.

Key issues: Too many words to explain nothing, Long run on paragraphs that aim to make the eyes glaze over. Should the entire manifesto be even printed within the article instead of just being left as an external link? An absurd amount of hideous buzzwords complimenting the look as a cult manifesto. The porthole portal of links in the middle of the article, spinning potential readers about into a traffic circle of useless information.

Trying to summarize for a more concise article: Agile is a hope & pray type philosophy towards development schemed up by people who don't know software development. It relies on being a constantly moving target with irresponsibly short goals, and overrelies on kissing the butt of a potential customer by overcommunicating with them daily. If left to their own devices, Agile developers would skip many of the standards and testing required of them by ISO and other such associations. Documentation is considered a devil of the details and other people should document the code made in 24 hours on a 7 hour coffee bender. 2601:540:C700:42DF:76C8:5F43:53F1:5C95 (talk) 06:49, 27 July 2023 (UTC)

Interesting summary. Not completely off the mark, but hyperbolic, negative, pessimistic and fear-based. Stevebroshar (talk) 12:19, 25 April 2024 (UTC)