Content deleted Content added
Mindmatrix (talk | contribs) m Reverted edit by Oreofrappe619 (talk) to last version by JnpoJuwan |
KMaster888 (talk | contribs) ce |
||
Line 10:
* '''Responding to change''' over following a plan
The practitioners cite inspiration from new practices at the time including [[extreme programming]], [[Scrum (software development)|scrum]], [[dynamic systems development method]], [[adaptive software development]] and being sympathetic to the need for an alternative to documentation driven, heavyweight software development processes.
Many software development practices emerged from the agile mindset. These agile-based practices, sometimes called ''Agile'' (with a capital A)<ref>{{cite web|url=https://www.rallydev.com/blog/engineering/agile-capital-vs-agile-lowercase |title=Agile With a Capital "A" Vs. agile With a Lowercase "a" |last=Rally |date=2010 |archive-url=https://web.archive.org/web/20160105105258/https://www.rallydev.com/blog/engineering/agile-capital-vs-agile-lowercase |archive-date=5 January 2016 |url-status=unfit |access-date=9 September 2015 }}</ref> include requirements, discovery and solutions improvement through the collaborative effort of [[Self-organizing communities|self-organizing]] and [[cross-functional team|cross-functional]] teams with their [[Customer|customer(s)]]/[[End user|end user(s)]].{{sfn|Collier|2011}}<ref name="WhatIsAgile">{{cite web|url = http://www.agilealliance.org/the-alliance/what-is-agile/|title = What is Agile Software Development?|date = 8 June 2013|access-date = 4 April 2015|publisher = Agile Alliance}}</ref>
| |||