Difference between revisions of "Agile (glossary)"
Jump to navigation
Jump to search
m (Text replacement - "<center>'''SEBoK v. 2.6, released 13 May 2022'''</center>" to "<center>'''SEBoK v. 2.6, released 20 May 2022'''</center>") |
|||
| (30 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
| − | ''<blockquote> | + | ''<blockquote>(1) Response ability state marked by high competence at both proactive and reactive change.'' (Dove 2001, 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.”'' (INCOSE 2011, 40, 183) </blockquote> | |
| − | + | ||
| + | ===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 Handbook'', version 3.2.2. San Diego, CA, USA: International Council on Systems Engineering (INCOSE). INCOSE-TP-2003-002-03.2.2. | ||
===Discussion=== | ===Discussion=== | ||
| − | + | None. | |
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
| + | |||
| + | <center>'''SEBoK v. 2.6, released 20 May 2022'''</center> | ||
Revision as of 06:29, 18 May 2022
(1) Response ability state marked by high competence at both proactive and reactive change. (Dove 2001, 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.” (INCOSE 2011, 40, 183)
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 Handbook, version 3.2.2. San Diego, CA, USA: International Council on Systems Engineering (INCOSE). INCOSE-TP-2003-002-03.2.2.
Discussion
None.