Building on the Center report, , this conversation examines successful contracting methods for software-intensive programs.
The U.S. Army鈥檚 first contract with the Wright Brothers in 1907 for an aircraft purchase was a scant two pages. Fast forward to 1955, the Navy鈥檚 F-4 Phantom II development specification fit on two pages. Just a few years later, the Air Force鈥檚 TFX aircraft contract required 250 pages, and in 1965 the C-5A transport aircraft came in at 1,500 pages. Long lists of specifications and contract data requirements have slowed down defense business practices. It conflicts with modern software development and can drive away the firms government needs most. How can contracting support the software development methods proven to work in the commercial sector?
- Can defense contracting align with agile/devops principles?
- When is modular contracting the right strategy, and how is accountability assured?
- What is the minimum necessary rights for DoD to avoid vendor lock?
- How can consumption-based solutions help expand the 鈥渁s a service鈥 model?
- What is possible today to make defense contracting recognizable to nontraditional firms?
Background听 Information
- 听
听