This article is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
This article is within the scope of WikiProject Spoken Wikipedia, a collaborative effort to improve the coverage of articles that are spoken on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
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.
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 18.104.22.168 (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)
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 22.214.171.124 (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)
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 126.96.36.199 (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.
Pathological laziness := compulsion to avoid work so obsessively, that it would have been less work to work. JonRichfield (talk) 06:13, 24 July 2014 (UTC)
I can confirm that the "maximizing" phrasing is not a typo. This is a direct quote from the "Principles behind the Agile Manifesto", which is one of the seminal documents for Agile software development. Spring (talk) 01:16, 1 September 2014 (UTC)