Difference between revisions of "Agile (glossary)"
Jump to navigation
Jump to search
(Created page with '''<blockquote>A comprehensive, integrated plan that identifies the acquisition approach and describes the business, technical, and support strategies that management will follow ...') |
|||
| Line 1: | Line 1: | ||
| − | ''<blockquote> | + | ''<blockquote>—(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) </blockquote>'' |
====Source==== | ====Source==== | ||
Revision as of 00:55, 17 May 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
DAU. February 19, 2010. Defense Acquisition Guidebook (DAG). Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense (DoD).
Discussion
Discussion as to why this is the "consensus" definition for the SEBoK.