Policy changes are often dynamic and occur quickly, but they can only create impact once implemented. The Eligibility APIs Initiative at 18F shares an example from their work that shows the potential for rapid, accurate policy implementation as code.
18F describes journey mapping: a visualization of the major interactions shaping a user’s experience of a product or service. This allows design teams to view a service through the perspective of the user and incorporate their learnings throughout the development process.
Government solicitations to procure custom software are often long, complicated, and take months. By using 18F’s agile contract format, agencies can hire an agile software contractor with a quickly-written dozen-page solicitation, allowing for immense savings in time and money.
It is frequently assumed that when rules are implemented as code, a rules engine is necessary. However, it is possible for policy people and engineers to effectively work together to code logic that drives technological system without needing a mediating rules engine at all.
18F describes modular contracting, the process of breaking up large, custom software procurements into a small constellation of smaller contracts. Modular procurement requires agile, product thinking, user-centered design, DevSecOps, and loosely-coupled architecture.
Few large government software projects are successful, as current ecosystems in place at agencies do not support agile development practices. This guide provides instructions to federal agencies on how to effectively budget for, procure, and oversee software development projects.
