FedBizOpps

OpenFBO: re-imagining the next generation FedBizOpps

Posted on by Luke Fretwell

OpenFBO

Say hello to OpenFBO.

Inspired by a recent General Services Administration request for information to create a “new and improved” FedBizOpps, OpenFBO is a community experiment to re-imagine the next generation FBO.

After reading GSA’s RFI, and working with NuCivic and CivicActions on their own submissions, I began thinking about what I would do if I was in charge of FedBizOpps, leaning on what’s been done with FBOpen, OpenRFPs and particularly former Philadelphia Chief Data Officer Mark Headd’s leadership and experiments with GitHub-based procurement.

I started thinking, what if the RFI, request for proposal, the development of FedBizOpps and everything around it was more open and collaborative. What if all RFIs and RFPs were public repos where anyone could engage more in the procurement process? What are the other possibilities for making the process fair for small businesses? How can it be a more enjoyable experience for the federal workers who need to use it on a daily basis.

Inspired by Mark’s idea of GitHub-based procurement, I created a simple brand (“OpenFBO”) and website (openfbo.org) using GitHub pages, and am leveraging GitHub’s issues feature for idea submissions. There are currently two repos (one for the website and one for the first RFI).

As with any project like this, it’s also a way for me to learn more about the federal procurement process in the context of a community project. I have a lot to learn and hope OpenFBO is the mechanism for doing so. I imagine this will also open my eyes to community engagement via GitHub, which I’m really looking forward to.

To get involved with OpenFBO, connect on GitHub, Twitter, LinkedIn or subscribe to the newsletter.

So, to start things off, we’re issuing our first RFI:

“How would you make FedBizOpps better?“

GSA takes a big step towards baking agile into federal procurement

Posted on by Luke Fretwell

The U.S. General Services Administration is working to make it easier for agencies to procure agile development services via a government-wide blanket purchase agreement, which could be finalized as early as the end of this year.

GSA initiated the effort with a request for information and an Agile Delivery Services Industry Day tentatively scheduled for Tuesday, January 27, from 1:00 to 3:00 p.m. eastern time.

According to GSA, the industry day aims to discuss “establishing a new, governmentwide Blanket Purchase Agreement (BPA), which will feature vendors specializing in agile delivery services (e.g.; user-centered design, agile software development, and DevOps).”

To get a better understanding each vendors qualifications and understanding for the agile process, the RFI asks each to explain in 500 words how they would improve the federal government business portal, FedBizOpps. Responses are due by January 23.

From the RFI:

To ascertain your agile delivery capabilities, the government is requesting that you describe how you would approach creating a new and improved version of an existing government digital service called FedBizOpps (FBO).

FBO, which you can view at http://www.fbo.gov, is used by government buyers to share information on federal business opportunities with the public. The system is intended to serve as the central portal for federal agencies to solicit products and services from commercial vendors in support of their missions. Using FBO, vendors can search, monitor, and retrieve opportunities solicited by the entire federal contracting community.

Based on this brief description of FBO, how would you go about designing, developing, testing, deploying and/or operating a new and improved system that produces such outcomes as user needs being met, risk of overall project failure (in terms of cost, schedule, quality) being mitigated, the architecture being adaptive to change, and taxpayer dollars being spent efficiently and effectively? Please be sure to include a listing of all the labor categories your company would use in this effort.

GSA will start an alpha test phase within “2-3 months” that will include vendors currently on Schedule 70 and apply only to GSA procurement, particularly to help “18F’s burgeoning delivery services team.” Afterwards, within 6-8 months, a beta phase will work to establish a government-wide BPA for procuring agile services.

“To keep pace, software acquisitions need to move at the speed of agile development cycles,” write 18F’s Chris Cairns and Greg Godbout in a blog post announcing the effort. “Ideally, this means less than 4 weeks from solicitation to contract kickoff, and from there no more than 3 months to deliver a minimum viable product (MVP).”

Bonus: RFI tips

Here are a few ideas you can use for your RFI submission:

  • Start with “API first.” FedBizOps desperately needs a more useful way to access the information available, especially newly-posted RFIs and requests for proposals.
  • Push all the front-end code to GitHub, where you’ll publicly address interface issues.
  • For design inspiration, start with FBOpen. Emphasize you’ll make searching easier and less convoluted. If you’re not familiar with this project or its predecessor RFP-EZ, start here.
  • Put all support/FAQs into Zendesk, much like the Federal Communications Commission has done with its new consumer complaint website.