
The Department of Defense (DoD) wants to save you from poor Agile development practices. “The purpose of this document is to provide guidance to DoD program executives and acquisition professionals on how to detect software projects that are really using agile development versus those that are simply waterfall or spiral development in agile clothing (‘agile-scrum-fall’),” reads the document issued by the department, helpfully titled: “DIB Guide: Detecting Agile BS” (PDF). (For those who don’t work in the depths of the Pentagon, the DIB is the Defense Innovation Board, an organization set up to improve the DoD’s technological innovation. Advisors on the board include Eric Schmidt, the former CEO of Google, who knows a thing or two about managing software-development teams.) The document breaks down core Agile values, which include:
- Individuals and interactions over processes and tools.
- Working software over comprehensive documentation.
- Customer collaboration over contract negotiation.
- Responding to change over following a plan.
- “Competence trumps process.”
- “Minimize time from program launch to deployment of simplest useful functionality.”
- “Adopt a DevSecOps culture for software systems.”
- “Software programs should start small, be iterative, and build on success ‒ or be terminated quickly.”