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!
===Quality focus=== [[File:Pair programming 1.jpg|thumb|right|[[Pair programming]], an agile development technique used in [[Extreme Programming|XP]]]] Specific tools and techniques, such as [[continuous integration]], automated [[unit testing]], [[pair programming]], [[test-driven development]], [[Software design pattern|design patterns]], [[behavior-driven development]], [[domain-driven design]], [[code refactoring]] and other techniques are often used to improve quality and enhance product development agility.<ref>{{cite book|last1=Jeffries|first1=Ron|last2=Anderson|first2=Ann|last3=Hendrickson|first3=Chet|title=Extreme Programming installed|date=2001|publisher=Addison-Weslsy|isbn=978-0201-70842-4|pages=[https://archive.org/details/extremeprogrammi00jeff/page/72 72β147]|url=https://archive.org/details/extremeprogrammi00jeff/page/72}}</ref> This is predicated on designing and building quality in from the beginning and being able to demonstrate software for customers at any point, or at least at the end of every iteration.<ref>{{cite book|title=Agile Testing: A Practical Guide for Testers and Agile Teams|author=Lisa Crispin|author2=Janet Gregory|publisher=Addison-Wesley|year=2009}}</ref>
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)