Agile Methods: Selected DoD Management and Acquisition Concerns

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, Considerations for Using Agile in DoD Acquisition (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.</p

Results of SEI Line-Funded Exploratory New Starts Projects

<p>The Software Engineering Institute (SEI) annually undertakes several line-funded exploratory new starts (LENS) projects. These projects serve to (1) support feasibility studies investigating whether further work by the SEI would be of potential benefit and (2) support further exploratory work to determine whether there is sufficient value in eventually funding the feasibility study work as an SEI initiative. Projects are chosen based on their potential to mature and/or transition software engineering practices, develop information that will help in deciding whether further work is worth funding, and set new directions for SEI work. This report describes the LENS projects that were conducted during fiscal year 2011 (October 2010 through September 2011).</p

Results of SEI Independent Research and Development Projects (FY 2010)

The Software Engineering Institute (SEI) annually undertakes several independent research and development (IRAD) projects. These projects serve to (1) support feasibility studies investigating whether further work by the SEI would be of potential benefit and (2) support further exploratory work to determine whether there is sufficient value in eventually funding the feasibility study work as an SEI initiative. Projects are chosen based on their potential to mature and/or transition software engineering practices, develop information that will help in deciding whether further work is worth funding, and set new directions for SEI work. This report describes the IRAD projects that were conducted during fiscal year 2010 (October 2009 through September 2010).</p