Talk:Agile software development
|This is the talk page for discussing improvements to the Agile software development article.|
|Archives: 1, 2|
|This article is of interest to the following WikiProjects:|
|Radiator (information) was nominated for deletion. The debate was closed on 09 August 2012 with a consensus to merge. Its contents were merged into Agile software development. The original page is now a redirect to here. For the contribution history and old versions of the redirected article, please see its history; for its talk page, see here.|
|The content of this article has been derived in whole or part from http://jaftalks.com/. Permission has been received from the copyright holder to release this material under both the Creative Commons Attribution-ShareAlike 3.0 Unported license and the GNU Free Documentation License. You may use either or both licenses. Evidence of this has been confirmed and stored by OTRS volunteers, under ticket number 2010051210011893. Note: Permission has been granted to incorporate content from this website under these licenses, but contributors to the article may determine through consensus whether content so incorporated is appropriate for inclusion.
This template is used by approved volunteers dealing with the Wikimedia Open Ticket Request System (OTRS) after receipt of a clear statement of permission at permissions-enwikimedia.org. Do not use this template to claim permission.
|Sources for development of this article may be located at|
I agree that the page needs to stay - however, what's with the parody song lyrics here? They shed no light on the subject and don't look very professional. (More "joke".)—Preceding unsigned comment added by 220.127.116.11 (talk) 19 April 2005
- Parody song lyrics no longer included in the current version of the article. Spring (talk) 01:03, 1 September 2014 (UTC)
XP, Scrum, Crystal, etc. are Agile Methods
The History sections says: "Methodologies similar to Agile created prior to 2000—include Scrum (1986), Crystal Clear, Extreme Programming (1996), Adaptive Software Development, Feature Driven Development, and DSDM (1995)." However, according to p. 396 of Sommerville's Software Engineering textbook (reference 7 in the article), these methodologies are different types of agile methods. Will someone confirm this and make the change? —Preceding unsigned comment added by 18.104.22.168 (talk) 19 November 2007
- Good point. The history section has changed significantly since you posted this, and the current version seems to have fixed this. Spring (talk) 01:01, 1 September 2014 (UTC)
Why is there no mention that this methodology gets most of its "new" ideas from the Free Software and/or Open Source development models used by those respective communities? —Preceding unsigned comment added by 22.214.171.124 (talk) 9 December 2010
Introduction is odd
"Agile software development is a group of software development methods based on iterative and incremental development.."
By the manifesto, as referenced later within the article, Agile software development is a set of values that partially order aspects of software development. These values may indeed be used to categorise methods but it is wrong to give the impression that Agile software development can be defined as a group of (think concrete set) development methods.
The Guide to Agile Practices also explicitly states that some agile approaches do away with iterations and that it is also possible to use iterative strategies which are not also incremental. It is clear that although typical, agile software development is definitely not based on iterative and incremental development. Polyhydra (talk) 12:35, 25 July 2014 (UTC)
- Based on that Intro, are there any other methods than Agile? (please don't point to the Myth Waterfall method - I've never been anywhere that uses that, as it just doesn't make practical sense. ZhuLien 126.96.36.199 (talk) 03:49, 29 July 2014 (UTC)
This is like reading an ad for Agile. Things like: "Since then, the Agile Movement, with all its values, principles, methods, practices, tools, champions and practitioners, philosophies and cultures, has significantly changed the landscape of the modern software engineering and commercial software development in the Internet era"
- I am here for the same reason. The article is an insult. It not only reads like a brochure, it even is illustrated like one, and a brochure for management at that, not for computer-literate readers or readers that wish to become computer-literate. Lots of handwaving and little substance. Those illustrations are the doo on the icing. I am removing the local one at least till someone tells me what they are to convey: that a member of their staff has an engaging smile? That software workers sit around monitors? Do us a favour! JonRichfield (talk) 08:34, 24 July 2014 (UTC)
I am a technical writer learning about the Agile method from Wikipedia. I noticed what must be a typo. Change "Simplicity—the art of maximizing the amount of work not done—is essential" to Simplicity—the art of minimizing the amount of work not done—is essential" — Preceding unsigned comment added by 188.8.131.52 (talk) 19:58, 1 July 2014 (UTC)
- I am new here too, not a technical writer, but a long-time computer man. There is no reason to think that was a typo.
- Think about it. It is poorly stated, but perfectly valid. You might find it helpful to consider the statement in the context of the following remarks dating back to the 1960s at the very least:
- Creative laziness is essential to a good computer man;
- Creative pathological laziness is essential to a great computer man.
The article currently reproduces the complete text of the Agile Manifesto, including a copyright notice that is incompatible with Wikipedia copyright policy. The external links section already contains a link to the Agile Manifesto. The section on the manifesto should paraphrase the manifesto loosely or otherwise summarize its contents. --Boson (talk) 21:45, 24 July 2014 (UTC)
The Manifesto specifically says "© 2001, the above authors. this declaration may be freely copied in any form, but only in its entirety through this notice."
Since there is the note on the webpage, and I think the creators of the Manifesto want it widely spread, I don't have any problem in leaving it in its entirety (as required) in the article. It's useful to have the text inline, instead of having to click to read it. Clemwang (talk) 21:29, 28 July 2014 (UTC)
- As I see it, we can reproduce material that
- is released in a form compatible with CC-BY-SA (which permits modification etc.) or
- is a fair use quotation (which would not normally permit quotation of the whole document).
- The copyright holder explicitly states "but only in its entirety through this notice", essentially releasing the work under CC-BY-ND, meaning that neither condition is fulfilled. According to the Creative Commons license article, CC-BY-NC and CC-BY-ND "are not free content licenses, according to definitions such as DFSG or the Free Software Foundation's standards, and cannot be used in contexts that require these freedoms, such as Wikipedia".
- If the copyright holders want it spread widely by means of Wikipedia, they should release it appropriately. --Boson (talk) 14:57, 29 July 2014 (UTC)
- "Guide to Agile Practices". Agile Alliance. Retrieved 25 July 2014.