search menu icon-carat-right cmu-wordmark

Agile Methods and Request for Change (RFC): Observations from DoD Acquisition Programs

Technical Note
This technical note looks at the evaluation and negotiation of technical proposals that reflect iterative development approaches that in turn leverage Agile methods.
Publisher

Software Engineering Institute

CMU/SEI Report Number
CMU/SEI-2013-TN-031
DOI (Digital Object Identifier)
10.1184/R1/6571853.v1
Subjects

Abstract

This technical note is the third in an SEI series on the adoption of lean and agile methods in the DoD. Agile topics in acquisition were introduced in CMU/SEI-2010-TN-002 and CMU/SEI-2011-TN-002. This technical note extends the topics covered into the evaluation and negotiation of technical proposals that reflect iterative development approaches that in turn leverage agile methods. This framework is intended for use by government program office personnel who seek to understand evaluation approaches in this context. The information and recommendations contained in this report result from observations of defense acquisition programs wherein contractors employed iterative methods such as Agile software development methodology (hereafter referred to as “agile”). Key questions for discussion with the contractor are provided, along with agile perspectives on why certain items will be defined differently depending on whether the contractor is using agile or iterative methods for software development. The intended audience for this paper includes any government personnel who need to support or participate in negotiations with contractors for changes to the contract that is in place to develop software using agile or iterative methods.

Cite This Technical Note

Lapham, M., Bandor, M., & Wrubel, E. (2014, January 24). Agile Methods and Request for Change (RFC): Observations from DoD Acquisition Programs. (Technical Note CMU/SEI-2013-TN-031). Retrieved June 22, 2024, from https://doi.org/10.1184/R1/6571853.v1.

@techreport{lapham_2014,
author={Lapham, Mary Ann and Bandor, Michael and Wrubel, Eileen},
title={Agile Methods and Request for Change (RFC): Observations from DoD Acquisition Programs},
month={Jan},
year={2014},
number={CMU/SEI-2013-TN-031},
howpublished={Carnegie Mellon University, Software Engineering Institute's Digital Library},
url={https://doi.org/10.1184/R1/6571853.v1},
note={Accessed: 2024-Jun-22}
}

Lapham, Mary Ann, Michael Bandor, and Eileen Wrubel. "Agile Methods and Request for Change (RFC): Observations from DoD Acquisition Programs." (CMU/SEI-2013-TN-031). Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, January 24, 2014. https://doi.org/10.1184/R1/6571853.v1.

M. Lapham, M. Bandor, and E. Wrubel, "Agile Methods and Request for Change (RFC): Observations from DoD Acquisition Programs," Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, Technical Note CMU/SEI-2013-TN-031, 24-Jan-2014 [Online]. Available: https://doi.org/10.1184/R1/6571853.v1. [Accessed: 22-Jun-2024].

Lapham, Mary Ann, Michael Bandor, and Eileen Wrubel. "Agile Methods and Request for Change (RFC): Observations from DoD Acquisition Programs." (Technical Note CMU/SEI-2013-TN-031). Carnegie Mellon University, Software Engineering Institute's Digital Library, Software Engineering Institute, 24 Jan. 2014. https://doi.org/10.1184/R1/6571853.v1. Accessed 22 Jun. 2024.

Lapham, Mary Ann; Bandor, Michael; & Wrubel, Eileen. Agile Methods and Request for Change (RFC): Observations from DoD Acquisition Programs. CMU/SEI-2013-TN-031. Software Engineering Institute. 2014. https://doi.org/10.1184/R1/6571853.v1