Wagile software development
Software development |
---|
Core activities |
Paradigms and models |
Methodologies and frameworks |
Supporting disciplines |
Practices |
Tools |
Standards and Bodies of Knowledge |
Glossaries |
Defined[edit]
Wagile software development is a group of software development methodologies that result from attempting to implement Agile in environments not ideally suited to or ill-prepared for this methodology, where the resulting approach is a combination of agile and waterfall methodologies.
Article excerpt[edit]
Going ‘Wagile’ ...Some teams turn to agile practices to dig their way out of failing projects, said Forrester analyst Peter Sterpe. “They do two-week iterations, engage in frequent, intentional communication, and do frequent builds.”
But that’s not agile development, he said. “They are simply getting a little bit iterative to put their projects back on track.”
- deJong, Jennifer Agile Principles Are Changing Everything. 2008.
Further reading[edit]
- Gorman, Jason. Phase Transition Illustrates Waterfall-Agile (or is it "WAgile")?. 2008.
- Gorman, Jason. The WAgile Software Development Life Cycle. 2008.
- Scrum: It Depends on Common Sense.
See also[edit]
- Nicolette, Dave. Slouching Towards Waterfall. 2006.
This article "Wagile software development" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Wagile software development. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.