Agile Methods: Selected DoD Management and Acquisition Concerns

Abstract : This technical note (TN), the second in an SEI series on Agile in the DoD, addresses some of the key issues that either must be understood to ease the adoption of Agile or are seen as potential barriers to adoption of Agile in the DoD acquisition context. These topics were introduced in the first TN of the series, CMU/SEI-2010-TN-002. For this TN, the SEI gathered more data from users of Agile methods in the DoD and delved deeper into the existing body of knowledge about Agile before addressing them. Topics considered here include: why DoD is interested in Agile methods; what it means to be Agile in the DoD; managing and contracting for Agile programs; technical milestone reviews in a DoD Agile acquisition context; estimating in a DoD Agile acquisition context; and moving toward adopting Agile practices. The authors hope that this report continues to stimulate discussion about and appropriate adoption of Agile in the DoD and federal agencies.

[1]  D. Conner,et al.  Building commitment to organizational change. , 1982 .

[2]  W. R. Howard.  Agile Project Management: Creating Innovative Products , 2010 .

[3]  Mary Poppendieck,et al.  Lean Software Development , 2007, 29th International Conference on Software Engineering (ICSE'07 Companion).

[4]  Suzanne Garcia,et al.  CMMI Survival Guide: Just Enough Process Improvement , 2006 .

[5]  A. James.  2010 , 2011, Philo of Alexandria: an Annotated Bibliography 2007-2016.

[6]  Capers Jones,et al.  Patterns of software system failure and success , 1996 .

[7]  Frederik D. Wiersema,et al.  The Discipline of Market Leaders-Choose your customers , 2015 .

[8]  Günther Ruhe,et al.  Product Release Planning - Methods, Tools and Applications , 2010 .

[9]  William L. Scherlis,et al.  Critical Code: Software Producibility for Defense , 2012 .

[11]  G. G. Stokes.  "J." , 1890, The New Yale Book of Quotations.

[12]  Richard Stutzke.  Estimating Software-Intensive Systems: Projects, Products, and Processes (Sei Series in Software Engineering) , 2005 .

[13]  Maya Ingle,et al.  Incorporating Vital Factors in Agile Estimation through Algorithmic Method , 2009, Int. J. Comput. Sci. Appl..

[14]  Geoffrey A. Moore.  Crossing the chasm : marketing and selling high-tech products to mainstream customers , 1999 .

[15]  Suzanne Garcia,et al.  Limits to the Use of the Zachman Framework in Developing and Evolving Architectures for Complex Systems of Systems , 2009 .

[16]  Amr Elssamadisy,et al.  Agile Adoption Patterns: A Roadmap to Organizational Success , 2008 .

[17]  T. Sulaiman,et al.  AgileEVM - earned value management in Scrum Projects , 2006, AGILE 2006 (AGILE'06).

[18]  Theresa Berousek,et al.  November, 2010 , 2011, The Lancet Neurology.

[19]  Mary Ann Lapham,et al.  Considerations for Using Agile in DoD Acquisition , 2010 .

[20]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[21]  Mike Cohn,et al.  Agile Estimating and Planning , 2005 .

[22]  H. Tohidi,et al.  Organizational culture and leadership , 2012 .

[23]  P ? ? ? ? ? ? ? % ? ? ? ? , 1991 .

[24]  W. R. Howard.  Lean – Agile Software Development: Achieving Enterprise Agility , 2010 .

[25]  Craig Larman,et al.  Agile and Iterative Development: A Manager's Guide , 2003 .

[26]  Aaron J. Shenhar,et al.  Adapting Your Technological Base: The Organizational Challenge , 2007 .

[27]  Jerry Avorn.  Technology , 1929, Nature.

[28]  S. M. Kinsella.  Activity-Based Costing: Does it Warrant Inclusion in a Guide to the Project Management Body of Knowledge (PMBOK® Guide)? , 2002 .

[29]  Jim Cooper,et al.  House Armed Services Committee Panel on Defense Acquisition Reform Findings and Recommendations , 2010 .