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!
=== Agile vs. waterfall === One of the differences between agile software development methods and waterfall is the approach to quality and testing. In the [[waterfall model]], work moves through [[software development life cycle]] (SDLC) phases—with one phase being completed before another can start—hence the '''''testing phase''''' is separate and follows a '''''build phase'''''. In agile software development, however, testing is completed in the same iteration as programming. Because testing is done in every iteration—which develops a small piece of the software—users can frequently use those new pieces of software and validate the value. After the users know the real value of the updated piece of software, they can make better decisions about the software's future. Having a value retrospective and software re-planning session in each iteration—[[Scrum (software development)|Scrum]] typically has iterations of just two weeks—helps the team continuously adapt its plans so as to maximize the value it delivers. This follows a pattern similar to the [[PDCA|plan-do-check-act]] (PDCA) cycle, as the work is ''planned'', ''done'', ''checked'' (in the review and retrospective), and any changes agreed are ''acted'' upon. This iterative approach supports a ''product'' rather than a ''project'' mindset. This provides greater flexibility throughout the development process; whereas on projects the requirements are defined and locked down from the very beginning, making it difficult to change them later. Iterative product development allows the software to evolve in response to changes in business environment or market requirements.
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)