Guides · Working software

Working software in Agile development

10 November 2026 · Escherbridge

GAO's Agile Assessment Guide describes Agile as incremental software development that emphasizes early and continuous delivery of working software. The useful test, for a delivery lead, is whether working software actually arrived — not whether a method was named in a slide. If the method's name is on the slide and working software is not in the hands of the people who have to use it, the name is not the result.

This is a delivery test, not a post about clients we do not have, and not a failure-rate listicle. It does not use Standish CHAOS numbers, and it does not invent "X percent of IT projects fail." The document cited here is the September 2020 Exposure Draft of the GAO Agile Assessment Guide. It is not called a later finalized edition, because a later edition was not opened.

the GAO Agile Assessment Guide, Agile Assessment Guide: Best Practices for Agile Adoption and Implementation, September 2020. The product page: published 28 September 2020, publicly released the same date. The PDF cover and preface treat it as an Exposure Draft, with a comment window "From September 28, 2020 through September 27, 2021," and the preface states that "GAO plans to periodically update this exposure draft based on users' experience and comments."

How the guide names the method: "One framework for incremental development is Agile software development, which has been adopted by many federal agencies. It emphasizes early and continuous software delivery and is defined by values and principles that can be realized through a set of common practices seen in specific Agile frameworks, such as DevOps, eXtreme Programming, Lean, Kanban, Scrum, and others."

On risk, in GAO's words, not as a guarantee: "With its emphasis on early and continuous delivery of working software, Agile can be a valuable tool for organizations in helping to mitigate schedule and budget risks." "Agile is the name we use to describe incremental software development methods in this guide, with concepts from Lean, Kanban, DevOps, or other more specific methods." "This Agile Guide is intended to address generally accepted best practices for Agile adoption, execution, and control." It is written to aid "federal agencies, departments, and auditors."

What GAO actually says

Incremental development; early and continuous delivery of working software; a family of methods (Scrum, Kanban, Lean, DevOps, XP), not one badge. A valuable tool for schedule and budget risk — in GAO's words — not a guarantee. The document is a September 2020 exposure draft of generally accepted best practices, aimed at federal agencies and auditors. It is not a private-sector certification, and it is not a certificate OVERSEASGENAI holds.

The siblings in this batch take up the same draft from two other angles: what an MVP is, and verifiable requirements. The live essay Each wave ends with a check is a house sibling, not a source.

The first conversation still ends with a yes, a no, or a better idea. That starts at Start. The self-serve dashboard remains "opening soon," not "available now."

The useful next step is to ask whether working software arrived, or to read the exposure draft itself. If something on this page is wrong, write to us.

Author: Escherbridge. Last reviewed: 2026-11-10, America/Denver.