-
Two agencies participating in the Digital Acquisition Accelerator pilot
on June 15, 2016
Today, we’re thrilled to announce that the Federal Bureau of Investigation and the U.S. Department of the Treasury are the first two agencies to participate in the Digital Acquisition Accelerator Pilot.
-
Announcing the launch of the Digital Acquisitions Pilot
on March 10, 2016
The Office of Federal Procurement Policy (OFPP) released a memorandum today that encourages agencies across the federal government to pursue innovative approaches to acquiring goods and services. Given the growing importance of digital acquisitions, OFPP is also launching a Digital Acquisitions Pilot along with the memo.
-
The EPA's new Environmental Digital Services marketplace
on December 3, 2015
The Environmental Protection Agency (EPA) is working on ways to contract with high-quality digital service vendors, which is why they just released a Request for Information (RFI) for creating an Environmental Digital Services marketplace.
-
The current future of 18F marketplaces
on November 18, 2015
In August, we announced the Full-stack Development Pool vendors for the Agile Delivery Services Marketplace. As we continue to work on the alpha version of this marketplace, we're beginning to plan out additional micro-markets as well.
-
Preventing technical debt
on October 22, 2015
In the final part of our series on technical debt, we talk about ways to minimize accumulating bad or unnecessary technical debt in the first place.
-
Announcing 18F Consulting’s Digital Economy Practice
on October 7, 2015
We’ve come to realize that there may be opportunities to achieve high impact in targeted areas by aligning our subject expertise with our digital expertise. To test our hypothesis, we’re launching an alpha version of our first policy vertical (or niche market) within 18F Consulting: the Digital Economy Practice.
-
Managing technical debt
on October 5, 2015
In the last post in this series, we talked about the potential consequences of having a lot of technical debt. Now, we’ll give you concrete steps to identify and then manage that technical debt so it doesn’t get out of hand.
-
What is technical debt?
on September 4, 2015
In part two of our series on technical debt, we define what technical debt is and how it can negatively impact your organization or project.
-
Announcing the Agile BPA awards: A conversation about the process
on August 28, 2015
As the first Agile BPA awards are now being issued, we asked three members of the team about the process and the lessons they’ve learned so far.
-
Don’t underestimate the danger of technical debt
on August 7, 2015
Technical debt is a financial metaphor that software developers use to talk to managers about the “hidden” costs associated with a system’s architecture and codebase. Over a series of upcoming posts, we’re going to explain what technical debt is, how to manage it, and some ways to prevent accumulating it.
-
Avoiding cloudfall: A systematic approach to cloud migration
on June 22, 2015
18F has been working on reducing the costs of entry to the cloud and thinking about good practices for cloud migration. One good practice is to adopt a scaled approach to cloud migration to avoid cloudfall.
-
The Agile Delivery BPA is here!
on June 15, 2015
The Request for Quotation (RFQ) for the Agile Delivery Services Blanket Purchase Agreement (Agile Delivery BPA) is hitting the street on Wednesday, June 17, 2015.
-
Agile development’s secret weapon: transparency
on April 24, 2015
18F Consulting recommends agile development for several reasons, including agile’s emphasis on user needs, continuous integration, and rapid adaptation to changed circumstances. But there is another important reason we recommend agile: its focus on transparency.
-
Coming soon: the agile delivery services solicitation
on April 23, 2015
Calling all agile vendors...get ready! By the end of this month, GSA will be releasing a Request for Quote (RFQ) for the alpha version of the Agile Delivery Services Blanket Purchase Agreement
-
New RFP ghostwriting service to improve contract success
on March 30, 2015
A poorly written RFP will expose you to such risks as overbidding to compensate for uncertainty, vendor lock-in, and catastrophic failure due to miscommunication and misunderstanding. You don’t want that. The taxpaying public doesn’t want that. And neither does 18F.
-
Labor category descriptions for agile procurements
on March 10, 2015
Clients of 18F Consulting frequently ask for help defining labor categories for agile contracts. We’ve published these definitions in a public GitHub repo so other acquisition professionals can benefit from them, too. Read on for more details.
-
Highlights from the Agile Delivery Services Industry Day events
on February 12, 2015
18F and GSA’s Office of Integrated Technology Services (ITS) held a pair of events for our upcoming Agile Delivery Services blanket purchase agreement (BPA). Over 700 people registered for the events, showing just how much interest there is from the private sector in this new BPA.
-
Creating a federal marketplace for agile delivery services
on January 8, 2015
The federal government and industry community have been talking about the need for software acquisitions to keep pace with technology cycles — typically 1-3 years. In today’s dynamic environment, however, not even that is fast enough.
-
User-centered design at 18F: a design studio for natural resource revenues
on September 25, 2014
We recently kicked off a new project with the Department of the Interior’s Office of Natural Resources Revenue (ONRR). Three weeks into the project, we decided to hold a design studio to solve the problem of how to convey complex revenue data. We needed to better understand the difference between onshore revenue (revenue from natural resources extracted from land) and offshore revenue (revenue from resources extracted from Federal offshore or the U.S. outer continental shelf) as it relates to our system. What is a design studio, you ask...
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock (
) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.