“The 18F team has issued official recommendations for how agencies can reduce risk when adopting agile and user-centered design methodologies for developing software.”
“The De-Risking Government Technology Field Guide, released this week, focuses on what to do when buying software, writing contracts for support, choosing between contractor proposals and establishing metrics for development.”
“The guide represents the first comprehensive attempt by the digital services arm of the General Services Administration to help federal cross-functional teams avoid failed IT projects and compliments the Agile Budgeting & Oversight Guide for State Governments published in 2019.”
“Custom technology projects are broken down into three phases: planning, deciding what to buy and doing the work.”
“During the planning phase agencies are advised to empower a product owner to lead development, seek constant end user feedback, default to open source code, tightly scope development to avoid overspending, and rely on remote collaboration tools among other recommendations.”
“18F suggests an agile contract format, time and material contract types, and evaluation of proposals based on best practices, during the research and solicitation phase of custom agile development…” Read the full article here.
Source: 18F instructs federal agencies on ‘de-risking’ agile IT projects – by Dave Nyczepir, September 11, 2020. FedScoop.