Difference between revisions of "Agile (glossary)"

From SEBoK
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 ...')
 
m (Text replacement - "<center>'''SEBoK v. 2.6, released 13 May 2022'''</center>" to "<center>'''SEBoK v. 2.6, released 20 May 2022'''</center>")
(31 intermediate revisions by 9 users not shown)
Line 1: Line 1:
''<blockquote>A comprehensive, integrated plan that identifies the acquisition approach and describes the business, technical, and support strategies that management will follow to manage program risks and meet program objectives. The Acquisition Strategy should define the relationship between the acquisition phases and work efforts, and key program events such as decision points, reviews, contract awards, test activities, production lot/delivery quantities, and operational deployment objectives. (DAU February 19, 2010)</blockquote>''
+
''<blockquote>(1) Response ability state marked by high competence at both proactive and reactive change.'' (Dove 2001, 69)</blockquote>
  
====Source====
+
''<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>
DAU. February 19, 2010. ''Defense Acquisition Guidebook (DAG)''. Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense (DoD).  
+
 
 +
===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===
Discussion as to why this is the "consensus" definition for the SEBoK.
+
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.

SEBoK v. 2.6, released 20 May 2022