Handbook by 18F designed for executives, budget specialists, legislators, and other “non-technical” decision-makers who fund or oversee state government technology projects that receive federal funding and implement the necessary technology to support federal programs. It aids in setting projects up for success by asking the right questions, identifying the right outcomes, and equally important, empowering decision-makers with a basic knowledge of the fundamental principles of modern software design.
Governments around the world are sharing custom-built software already, and have done so for many years. It’s vital, cost-saving, and meets the needs of users. This article provides examples of a range of different software sharing models.
This report reviews the features of intergovernmental software cooperatives, examines several different examples, looks at different categories of cooperatives and their governance structures, and inventories known cooperatives both within and outside of the United States. Agencies rethinking how they obtain technical functionality, budget officials looking to control costs and outcomes, or private funders that want to improve public services may find this report particularly useful.
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.
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.
