gao-agile
GAO Agile Assessment Guide (GAO-24-105506, 2023)
Source: US Government Accountability Office (GAO) — US Government work, public domain | Chapters: 9
When to use
Use this skill when you need to assess, govern, or explain Agile software development in a federal program: choosing among Agile frameworks, diagnosing why an Agile transition is stalling, structuring requirements and a backlog, writing or judging an Agile-aware contract, applying cost/schedule/EVM discipline to iterative work, picking meaningful metrics, or running an audit against GAO best practices. It is GAO's oversight-and-acquisition companion to the agency SE handbooks and to the sibling cost, schedule, and technology-readiness guides.
Prerequisites: none — plain Markdown; no MCP server, API key, or licence tier needed at runtime.
How to Use This Skill
- Without arguments — load the core frameworks below for the mental model: Agile vs. Waterfall, the three adoption perspectives, the five planning levels, and how oversight discipline maps onto Agile artifacts.
- With a topic — ask about a framework (Scrum, Kanban, SAFe), an adoption challenge, user stories / INVEST, a definition of done, the product owner role, contracting (SOO/PWS/SOW, modular contracting), WBS / EVM / velocity, a metric (CFD, lead/cycle time), or an auditor question.
- With a chapter — ask for
ch03(adoption best practices),ch05(requirements),ch06(contracting),ch07(monitoring & EVM),ch08(metrics),ch09(auditor questions).
Supporting files: glossary.md, patterns.md, cheatsheet.md.