Difference between revisions of "Agile (glossary)"
(→Source) |
|||
Line 1: | Line 1: | ||
− | ''<blockquote>(1) Response ability state marked by high competence at both proactive and reactive change | + | ''<blockquote>(1) Response ability state marked by high competence at both proactive and reactive change. (Dove 2001, p. 69)</blockquote> |
− | ''<blockquote>(2) Project execution methods can be described on a continuum from “adaptive” to “predictive.” Agile methods exist on the “adaptive” side of this continuum, which is not the same as saying that agile methods are “unplanned” or “undisciplined.” | + | ''<blockquote>(2) [[Project (glossary)|Project]] execution methods can be described on a continuum from “adaptive” to “predictive.” Agile methods exist on the “adaptive” side of this continuum, which is not the same as saying that agile methods are “unplanned” or “undisciplined.” (179 INCOSE 2010) </blockquote>'' |
====Source==== | ====Source==== | ||
Line 9: | Line 9: | ||
===Discussion=== | ===Discussion=== | ||
− | + | There is currently no discussion for this term. This will be completed for SEBoK version 1.0. | |
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] |
Revision as of 17:01, 16 September 2011
(1) Response ability state marked by high competence at both proactive and reactive change. (Dove 2001, p. 69)
(2) Project execution methods can be described on a continuum from “adaptive” to “predictive.” Agile methods exist on the “adaptive” side of this continuum, which is not the same as saying that agile methods are “unplanned” or “undisciplined.” (179 INCOSE 2010)
Source
(1) Dove, R. 2001. Response Ability: The Language, Structure, and Culture of the Agile Organization. New York, NY, USA: John Wiley & Sons.
(2) INCOSE. 2011. INCOSE Systems Engineering hHandbook, version 3.2. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.
Discussion
There is currently no discussion for this term. This will be completed for SEBoK version 1.0.