-
Taking the ATO process from 6 months to 30 days
on July 19, 2018
Security compliance is a major factor in launching a software system in the federal government. The Authority To Operate compliance process for systems within our division of GSA was taking more than six months for every system. With the new process, we have cleared the backlog and reduced the turnaround time to under a month.
-
Five contracting tweaks that have yielded 18F better procurements (thus far)
on July 17, 2018
Here are five procurement hacks — both in the context of our Agile Blanket Purchase Agreement (BPA) and in general — that we’ve made in the past few years to make the procurement process a bit more joyful and effective.
-
The case for open source software
on July 12, 2018
Software is everywhere at Lawrence Livermore National Laboratory. Much of their software portfolio is open source. They began releasing software in the 1990s — long before the Federal Source Code Policy required government institutions to make their code available to each other and to release at least 20 percent to the public.
-
Introducing Accessibility for Teams
on July 10, 2018
The Accessibility Guild in the Technology Transformation Services (TTS) at the U.S. General Services Administration (GSA) set out to understand how people in different roles practice accessibility. We asked designers, developers, and product managers across our organization to share their accessibility practices, from self-testing to asking for help.
-
Ask 18F — How do you tackle the problem of associating plain language to formal governmental terms?
on July 6, 2018
Ask 18F is an advice column that answers questions sent in by federal employees. In this edition, we’ll talk about how to associate plain language to formal governmental terms
18F Blog
Delivering civic technology
Page 25 of 101