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.
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.
This guide introduces federal teams to the philosophy, principles, and practical methods of Agile development—emphasizing adaptability, collaboration, and continuous learning over rigid planning.
Testing (and re-testing) your designs with users will help you build the best possible product. Our Validate Methods cover varied testing scenarios and potential user groups.
The Decide Methods help you derive insights from the information gathered during the Discovery phase. You’ll validate initial assumptions, develop a deeper understanding of workflows and processes, and develop design hypotheses.
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.
