Please use this identifier to cite or link to this item:
https://dair.nps.edu/handle/123456789/1331
Full metadata record
DC Field | Value | Language |
---|---|---|
dc.contributor.author | David Tate | |
dc.date.accessioned | 2020-03-16T17:51:58Z | - |
dc.date.available | 2020-03-16T17:51:58Z | - |
dc.date.issued | 2016-05-05 | |
dc.identifier.citation | Published--Unlimited Distribution | |
dc.identifier.uri | https://dair.nps.edu/handle/123456789/1331 | - |
dc.description | Acquisition Management / Defense Acquisition Community Contributor | |
dc.description.abstract | Acquisition cycle time roughly speaking, the development lead time to field a working system once we have identified a need for a new materiel solution is a hot topic in defense circles. This work takes a data-driven look at historical and current acquisition program cycle times. We show that the trend toward longer cycle times over the past few decades is restricted to a handful of high-profile programs, which has profound implications for effective policy response. We also show evidence that cycle times are driven by system complexity, and that schedule slip is associated primarily with overly optimistic schedule estimates. We conclude with a discussion of the increasing importance of software for development lead times, and the general problem of trading capability for timeliness in acquisition programs. | |
dc.description.sponsorship | Acquisition Research Program | |
dc.language | English (United States) | |
dc.publisher | Acquisition Research Program | |
dc.relation.ispartofseries | Cycle Time | |
dc.relation.ispartofseries | SYM-AM-16-027 | |
dc.subject | Acquisition Cycle Time | |
dc.subject | Program Cycle Time | |
dc.title | Acquisition Cycle Time: Defining the Problem | |
dc.type | Article | |
Appears in Collections: | Annual Acquisition Research Symposium Proceedings & Presentations |
Files in This Item:
File | Size | Format | |
---|---|---|---|
SYM-AM-16-027.pdf | 544.22 kB | Adobe PDF | View/Open |
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.