The IT Law Wiki

Agile software development

32,079pages on
this wiki
Add New Page
Add New Page Talk0

Definition Edit

Agile software development is

calls for the delivery of software in small, short increments rather than in the typically long, sequential phases of a traditional waterfall approach. More a philosophy than a methodology, Agile emphasizes early and continuous software delivery, as well as using collaborative teams and measuring progress with working software, and promotes these four values: (1) individuals and interactions over processes and tools, (2) working software over comprehensive documentation, (3) customer collaboration over contract negotiation, and (4) responding to change over following a plan.[1]
not a set of tools or a single methodology, but a philosophy based on selected values, such as prioritizing customer satisfaction through early and continuous delivery of valuable software; delivering working software frequently, from every couple of weeks to every couple of months; and making working software the primary measure of progress.[2]

Overview Edit

Agile software development encompasses various Agile methodologies that share the same philosophy, but have their own practices and tactics. Some examples are Scrum, Kanban, DSDM, FDD, XP, etc. Based on the specific Agile methodology being used, note that the requirement document may vary.

References Edit

  1. Information Technology Reform: Agencies Need to Increase Their Use of Incremental Development Practices, at 9 n.25.
  2. Information Technology: Leveraging Best Practices to Help Ensure Successful Major Acquisitions, at 14 n.35.

Source Edit

Also on Fandom

Random Wiki