Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Agile software development
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== {{anchor|Agile principles}} Principles === The values are based on these principles:<ref name="ManifestoPrinciples"> {{cite web |url=http://www.agilemanifesto.org/principles.html |title=Principles behind the Agile Manifesto |year=2001 |publisher=Agile Alliance |author=Kent Beck |author2=James Grenning |author3-link=Robert Cecil Martin |author3=Robert C. Martin |author4=Mike Beedle |author5-link=Jim Highsmith |author5=Jim Highsmith |author6-link=Stephen J. Mellor |author6=Steve Mellor |author7=Arie van Bennekum |author8-link=Andy Hunt (author) |author8=Andrew Hunt |author9-link=Ken Schwaber |author9=Ken Schwaber |author10-link=Alistair Cockburn |author10=Alistair Cockburn |author11-link=Ron Jeffries |author11=Ron Jeffries |author12-link=Jeff Sutherland |author12=Jeff Sutherland |author13-link=Ward Cunningham |author13=Ward Cunningham |author14=Jon Kern |author15-link=Dave Thomas (programmer) |author15=Dave Thomas |author16-link=Martin Fowler (software engineer) |author16=Martin Fowler |author17=Brian Marick |access-date=6 June 2010 |archive-url=https://web.archive.org/web/20100614043008/http://www.agilemanifesto.org/principles.html |archive-date=14 June 2010 |url-status=live |author-link=Kent Beck }}</ref> # Customer satisfaction by early and continuous delivery of valuable software. # Welcome changing requirements, even in late development. # Deliver working software frequently (weeks rather than months). # Close, daily cooperation between business people and developers. # Projects are built around motivated individuals, who should be trusted. # Face-to-face conversation is the best form of communication (co-location). # Working software is the primary measure of progress. # Sustainable development, able to maintain a constant pace. # Continuous attention to technical excellence and good design. # Simplicity—the art of maximizing the amount of work {{Not a typo|not}} done—is essential. # Best [[Agile Architecture|architectures]], requirements, and designs emerge from self-organizing teams. # Regularly, the team reflects on how to become more effective, and adjusts accordingly.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)